Begin with the physical fact that the phrase tries to hide: optical fiber carries no electrical power at all. 'PoE over fiber' is therefore never a single cable doing both jobs — it is a family of hybrid architectures in which fiber carries the data across the long span, and PoE is generated, delivered or passed along at the places where copper and power legitimately exist. The phrase survives because the designs are real and common — every campus camera estate is one. This article maps the patterns and, more importantly, their power budgets, because hybrid links fail on watts, not on glass.
Pattern one: fiber to the cabinet, PoE from the cabinet
The dominant architecture. Fiber runs from the core to a field cabinet; at the cabinet, a PoE switch or a set of injectors (fed by the cabinet's local mains or DC plant) powers the cameras over copper runs inside the standard 100 m channel. The fiber link and the PoE links are separate citizens, each doing its native job. The cabinet is the marriage point, which is why cabinet power design — feed, backup, thermal — is the real engineering of this pattern. Media converters with PoE at the copper side collapse the cabinet further where the camera count is one or two.
Pattern two: the combination extender
The most instructive documented product in this space removes the cabinet's switch entirely: an extender in the manufacturer's range combining eight Gigabit PoE channels with six forward and two backward 3G-SDI channels on one fiber unit. Read that again as an architecture: at the remote end, one device lands the fiber, powers eight PoE camera channels, and carries the position's SDI traffic in both directions. It exists because real poles and cabinets are mixed-media, and because one engineered unit beats five boxes at the top of a pole. Where a position inventory shows PoE devices and SDI sharing a location, this pattern is the design's centre of gravity.
Pattern three: powered copper hops toward the fiber
The inverse geometry also occurs: the camera sits beyond copper reach of the cabinet, but the fiber lands at the cabinet. PoE extenders chain from the cabinet — each re-driving data and re-presenting power for a further 100 m channel, powered from the passing PoE itself — while the fiber does the long haul behind them. The chain's budget is the design: device peak draw, plus each hop's consumption, plus cable losses, must fit inside the feeding PSE's class, which is why these chains pair with the 802.3bt-class injectors at their head.
The budget arithmetic, once, carefully
Every hybrid pattern reduces to one ledger: power available at the source (PSE class: 30W at, or 60/90/100W bt), minus transport losses (cable runs, extender hops, splitter conversions), against power demanded at the worst moment (camera with heater and IR on, AP with all radios up). Two habits keep the ledger honest. First, worst-case loads, always — the bench average is a fiction the weather will correct. Second, margin for ageing and the device you will swap in during year three. A hybrid link designed at 97% of budget is a link designed to fail interestingly.
- Head end: PSE class and count (injector, switch port, or combination unit).
- Transport: hop count and per-hop consumption, copper run lengths.
- Load: per-device maximum draw, summed at the position, with the heater caveat.
- Margin: an explicit percentage, written on the design, not left in someone's head.
Choosing the pattern
Several cameras plus local power available: pattern one, the cabinet architecture — it scales and it is serviceable. A mixed-media position that must be one device: pattern two, the combination unit. A long thin spur with power only at the head: pattern three, budgeted hops. And the honest fourth answer, sometimes: pull local power to the position and let the fiber be fiber — trenching a power cable is occasionally cheaper than engineering around its absence, and a design process that cannot say so is selling, not designing. State the position inventory and the power reality in the inquiry, and the pattern — plus its budget, in writing — is what comes back.
Failure shapes, and designing against them
Hybrid links have characteristic failures that pure designs do not, and they are worth designing against explicitly. The single-point cabinet: pattern one's cabinet concentrates fiber landing, power and switching in one box — its feed and its thermal design deserve the redundancy thought the estate's importance implies. The invisible budget creep: pattern three's chain works at commissioning, then a camera is swapped for a hungrier model whose heater pushes the chain past its head-end class — the defence is the written margin and a note on the drawing naming the maximum load the chain was designed for. The mixed-position tangle: pattern two's combination unit simplifies the pole but concentrates it — sparing strategy (a shelved spare unit, or a documented fallback wiring) belongs in the design pack. None of these are arguments against hybrid links; they are the difference between a hybrid link as an architecture and as an improvisation. The estates that run for a decade are the ones whose improvisations were written down, budgeted and turned into designs.
Documenting the hybrid, so it stays one
The final discipline is paperwork, because hybrid links are the first thing organisational memory loses. The design pack for each position should record: the fiber route and strand assignment; the head-end PSE and its class; every hop device and its model; the load table with worst-case draws and the designed margin; and the power source with its backup arrangement. Five lines per position. With them, the year-three camera swap is a lookup ('does the new draw fit the recorded margin?') instead of an investigation, and the 3 a.m. fault is a bisection instead of an archaeology. Hybrid architecture is how real estates are built; the five lines are how they stay built.
There is a reason this hybrid pattern keeps winning designs despite its inelegant name: it matches how sites actually are. Power lives where buildings put it — in cabinets, plant rooms and pole bases with feeds of their own. Data wants to travel kilometres without caring. Copper is superb for the last hundred metres and hopeless for the first kilometre. The hybrid simply lets each medium do the leg it is good at, and pays for the honesty with a power budget that must be kept like a ledger. Estates that keep the ledger get a decade of indifference from their camera network. That indifference — the network nobody talks about — is the highest compliment infrastructure ever earns.