PoE Budget Calculator.
— PoE budget · IEEE 802.3 af / at / bt
Count what the switch must power today.
Aggregates per-device wattage per IEEE 802.3bt Type 1–4 class tables and adds 30% spare headroom for a five-year refresh. A planning figure, not a procurement spec.
Recommended budget
125 W
96 W expected draw + 30% headroom
Switch tier
Tier 1
24-port switch, 16 PoE+ ports · 190 W published pool · one chassis
Devices counted
8
your counts · 16 802.3at (PoE+) ports per chassis
Largest single device
18 W
IEEE 802.3at (PoE+) — sets the per-port floor
A planning link that reopens this exact configuration — not a quote.
The power pool is shared across ports — it is not a per-port allowance.
- sku class
- NETGEAR GS324P — 190 W shared across 16 of its 24 ports — engineering reference, not a quote
- powered ports
- 16 of 24 ports power 802.3at (PoE+) on one chassis · 8 devices counted · one chassis
- shared pool
- Budget is a shared pool across ports, not a per-port figure
- draw basis
- EXPECTED draw at the powered device — a planning figure for the family, not the datasheet maximum of any one model and not a measurement
- device counts
- USER INPUT — whatever you entered on the left
- switch pool
- MANUFACTURER MAX — 190 W published · Internal fixed supply; no PoE upgrade path
- port ceiling
- MANUFACTURER MAX — 25.5 W to the device on one port at this tier (IEEE PD ceiling)
- port count
- MANUFACTURER MAX — 16 of the 24 ports can power 802.3at (PoE+). Ports and watts are independent: this is what one chassis can terminate, whatever the pool
- class source
- IEEE 802.3 af / at / bt class tables
- channel loss
- Not modelled — the spare below has to cover it
- cabling
- TIA/EIA-568-C · ISO/IEC 11801 Cat6A
- headroom
- 30% — fixed, and not adjustable in this tool
The answer above sizes this load against an engineering tier. Name a switch the repository holds published figures for and the load is checked against that manufacturer’s own port count, per-port ceiling and aggregate pool instead.
+ Model assumptions (9)− Model assumptions
Indicative — class wattages per IEEE 802.3 af / at / bt tables; a switch PoE budget is a shared pool across ports, not a per-port figure. The wattages counted here are what each device draws at the powered end; a switch pool is quoted at the sourcing end, and the gap between them — plus cable loss over a long run — is not modelled and has to come out of the spare shown above. Tier budgets assume the power supplies named beside them; several of those chassis reach the stated pool only when both supply bays are populated. Production designs ship with a per-port budget allocation spreadsheet.
What changes this estimate
- Exact device models and their datasheet PoE class
- Cable-run lengths near the 100 m limit (PSE-to-PD derating)
- Device growth across the five-year refresh
- Which physical ports the rack schedule allocates — the count is modelled, the plan is not
A planning link that reopens this exact configuration — not a quote.
Those figures travel with you, labelled as carried and editable there. The 96 W carried is the expected device draw, before this tool’s 30% headroom — the network calculator’s own PoE figure carries none, so the two arrive on the same footing.
The Engineering Project Workspace opens with 4 cameras, 8 powered devices and 96 W of PoE load ready to add. Nothing is added until you choose to. This workspace is kept in this browser only. Nothing is uploaded, nothing reaches TechnoGuru, and clearing your site data clears it.
IT · Networking · IEEE 802.3
Count the PoE-powered devices on the network — phones, cameras, APs, intercoms, sensors, AV nodes — and the tool sizes the switch PoE budget, the IEEE 802.3 class each device needs, and the SKU class. 30% headroom is built in and fixed; there is no headroom control, because a five-year refresh is the assumption the whole figure rests on.
- PoE classes
- af · at · bt
- Headroom
- 30% fixed
- Switch tiers
- 6
- SKU class
- Aruba · Cisco · NETGEAR
Field notes · why the model is shaped this way
PoE budget is a shared pool
A 48-port PoE+ switch with 740 W cannot drive 30 W per port simultaneously — only about 24 of the 48 ports can run at the full 30 W at once.
High-draw devices need 802.3bt
Wi-Fi 7 APs draw about 32 W — above the 25.5 W a PoE+ port can deliver to the device — so specify 802.3bt Type 3 ports. Heated PTZ cameras at 55 W go past Type 3's 51 W device ceiling and need Type 4.
30% headroom is the rule
Five-year refresh cycles see device counts grow about 6% a year. 30% spare keeps the switch in budget across the cycle. It is applied unconditionally — the tool has no override, and a genuinely static device count is a conversation for the design review rather than a slider.
A named camera beats a category figure
The camera rows in the calculator are expected draws for a family. 343 camera models can be named instead, and 305 of them carry the manufacturer's own published maximum — which sets the pool, the IEEE class floor and the powered-port count together. The other 38 publish no maximum draw: naming one of those changes nothing about the wattage and the tool says so rather than inventing a figure. 13 profiles the catalogue has withdrawn are not offered at all.
This table has no conference-audio row
The device rows above are the families this planner models, and none of them is a microphone, a ceiling array or a conferencing DSP. The nearest row a boardroom fit-out can reach is the av-over-ip node at 18 W. Against the manufacturers' own published maxima for the 13 conferencing devices listed below, that row over-reserves for 12 of them, under-reserves for 1, and asks for a PoE+ port on 11 devices whose manufacturers state 802.3af is sufficient. One of each would reserve 234 W against a published 141.45 W. No category figure has been invented to close that — the published maxima are listed instead.
Ports are a second, independent limit
Watts and ports are sized separately and the answer is whichever is larger. A 24-port chassis terminates 24 powered devices however small their draw, so an estate of 25 low-wattage sensors needs a bigger switch even though the pool was never in question. The calculator above floors on port count as well as wattage and IEEE class, and says how many chassis the estate takes.
Conference audio on the same switch
13 conferencing devices whose own published maximum draw this estate holds.
Ceiling arrays, table arrays and conferencing DSP are PoE powered devices and they land on the same budget as the cameras and access points above. Of 19 conference-audio records across 3 brands, 13 across 2 publish a MAXIMUM draw and an IEEE family, which are the two figures a PoE budget cannot be computed without. 11 of them state that 802.3af is sufficient; 2 state a heavier family. Every figure below is read off the manufacturer’s own document and quoted as printed.
These devices are listed, not selectable in the calculator above. The calculator budgets a device against a family row, and this planner has no conference-audio family row — no expected wattage for that family can be substantiated from 2 brands, so none has been invented. Enter the published maximum below against your own count.
Sennheiser TeamConnect Ceiling 2ceiling array
8.8 Wpublished maximum
IEEE 802.3af · established from the pd class · 4.15 W under that family's device ceiling
“Power consumption max. 8.8 W”
“Supply voltage 44 – 57 V DC / PoE IEEE 802.3af Class 3”
The maximum draw is stated in a source naming this exact model. Read on assets.sennheiser.com, the document cited for this device, 2026-09-12.
Shure MXA902ceiling array
24 Wpublished maximum
IEEE 802.3at (PoE+) · established from the pd class · 1.5 W under that family's device ceiling
“24 W maximum”
“Power over Ethernet Plus (PoE+), Class 4”
The maximum draw is stated in a source naming this exact model. Read on www.shure.com, the document cited for this device, 2026-09-12.
Shure P300conferencing dsp
17.5 Wpublished maximum
IEEE 802.3at (PoE+) · established from the pd class · 8 W under that family's device ceiling
“Power Consumption: 17.5 W, maximum. Thermal Power Dissipation: Maximum 17.5 W (60 BTU/hr); typical 14.6 W (50 BTU/hr).”
“802.3 at Type 2 (PoE Plus), Class 4”
The maximum draw is stated in a source naming this exact model. Read on pubs.shure.com, the document cited for this device, 2026-09-12.
Shure MXCWAPTwireless system
12.95 Wpublished maximum
IEEE 802.3af · established from the pd class · sits exactly on that family's device ceiling
“Power Consumption: 12.95W (max), 6.5W (typ)”
“Power Over Ethernet, 802.3af, Class 0 PD (MXCW datasheet). The live MXCW user guide states the same supply less the clause number: "Supply Type — Power over Ethernet (PoE)" with "Supply Voltage — 37-57 V".”
The maximum draw is stated in a source naming this exact model. Read on pubs.shure.com, the document cited for this device, 2026-09-12.
Shure MXA925ceiling array
12.5 Wpublished maximum
IEEE 802.3af · established from the pd class · 0.45 W under that family's device ceiling
“12.5 W maximum”
“Power over Ethernet (PoE), Class 0”
The maximum draw is stated in a source naming this exact model. Read on www.shure.com, the document cited for this device, 2026-09-12.
Shure MXA901ceiling array
10.1 Wpublished maximum
IEEE 802.3af · established from the pd class · 2.85 W under that family's device ceiling
“10.1 W maximum”
“Power over Ethernet (PoE), Class 0”
The maximum draw is stated in a source naming this exact model. Read on www.shure.com, the document cited for this device, 2026-09-12.
Shure MXA920ceiling array
10.1 Wpublished maximum
IEEE 802.3af · established from the pd class · 2.85 W under that family's device ceiling
“10.1 W maximum”
“Power over Ethernet (PoE), Class 0”
The maximum draw is stated in a source naming this exact model. Read on www.shure.com, the document cited for this device, 2026-09-12.
Shure ANI4INconferencing dsp
10 Wpublished maximum
IEEE 802.3af · established from the pd class · 2.95 W under that family's device ceiling
“Power Consumption: 10W, maximum”
“Power over Ethernet (PoE), Class 0”
The maximum draw is stated in a source naming this exact model. Read on pubs.shure.com, the document cited for this device, 2026-09-12.
Shure ANI4OUTconferencing dsp
10 Wpublished maximum
IEEE 802.3af · established from the pd class · 2.95 W under that family's device ceiling
“Power Consumption: 10W, maximum”
“Power over Ethernet (PoE), Class 0”
The maximum draw is stated in a source naming this exact model. Read on pubs.shure.com, the document cited for this device, 2026-09-12.
Shure MXA710linear array
10 Wpublished maximum
IEEE 802.3af · established from the pd class · 2.95 W under that family's device ceiling
“10 W maximum”
“Power over Ethernet (PoE), Class 0”
The maximum draw is stated in a source naming this exact model. Read on www.shure.com, the document cited for this device, 2026-09-12.
Shure ANIUSB-MATRIXconferencing dsp
6.5 Wpublished maximum
IEEE 802.3af · established from the pd class · 6.45 W under that family's device ceiling
“Power Consumption: 6.5W, maximum. Thermal Power Dissipation: Maximum 6.8W (23.0BTU/hr); typical 6.0W (20.8BTU/hr). [Recorded as published — note Shure's own maximum dissipation figure (6.8 W) exceeds its stated maximum consumption (6.5 W); both are reproduced verbatim rather than reconciled.]”
“Power over Ethernet (PoE), Class 0. (PoE Plus compatible).”
The maximum draw is stated in a source naming this exact model. Read on pubs.shure.com, the document cited for this device, 2026-09-12.
Shure MXA320table array
5 Wpublished maximum
IEEE 802.3af · established from the pd class · 7.95 W under that family's device ceiling
“5 W maximum”
“Power over Ethernet (PoE), Class 0”
The maximum draw is stated in a source naming this exact model. Read on www.shure.com, the document cited for this device, 2026-09-12.
Shure MXA310table array
4 Wpublished maximum
IEEE 802.3af · established from the pd class · 8.95 W under that family's device ceiling
“4W, maximum”
“Power over Ethernet (PoE), Class 0”
The maximum draw is stated in a source naming this exact model. Read on www.shure.com, the document cited for this device, 2026-09-12.
Not listed, and why
6 of the 19 records are held back from the figures above. 6 publish no MAXIMUM draw and 4 publish no PoE class or clause. A typical, static, nominal or approximate figure is not a maximum, and promoting one into a budget would be inventing the number this page exists to avoid inventing.
AKG CGN341 E
absent: power.maxPowerDrawW — no published MAXIMUM draw · power.poeStandardRaw — no published PoE class or clause
AKG CS3 BU
absent: power.maxPowerDrawW — no published MAXIMUM draw · power.poeStandardRaw — no published PoE class or clause
published instead: “Power Supply SMPS 100‐240V (50Hz / 60Hz) 3A; Static Consumption 13W; Nominal Power Consumption 320W; Output Power <=90W / 24V each way. AKG publishes no 'maximum' draw — 13 W is stated as static and 320 W as nominal — so no maximum has been recorded.”
Sennheiser EW-DX TS 3-pin
absent: power.maxPowerDrawW — no published MAXIMUM draw · power.poeStandardRaw — no published PoE class or clause
published instead: “Input voltage 2.0 bis 4.35 V; Input current < 300 mA; Power supply BA 40 rechargeable battery pack. No wattage figure is published.”
Sennheiser TeamConnect Ceiling M Plus
absent: power.maxPowerDrawW — no published MAXIMUM draw
published instead: “Power consumption approx. 8 W”
powering: “Supply voltage: PoE IEEE 802.3af Class 3 or PoE IEEE 802.3at / Type 2 / Class 4 (when cascaded)”
Sennheiser TeamConnect Ceiling Medium
absent: power.maxPowerDrawW — no published MAXIMUM draw
published instead: “Power consumption approx. 8 W”
powering: “Supply voltage: PoE IEEE 802.3af Class 3 or PoE IEEE 802.3at / Type 2 / Class 4 (when cascaded)”
Shure MXCW640
absent: power.maxPowerDrawW — no published MAXIMUM draw · power.poeStandardRaw — no published PoE class or clause
published instead: “Power Consumption: 3 W, typical. (No maximum is published for normal operation — maxPowerDrawW deliberately omitted rather than inferred from the typical figure.) USB charging is specified separately: "USB — Input Voltage Range 4.5 - 5.25 V — Power Consumption 10 W maximum". Battery: Shure SB930 Lithium-Ion, 3 - 4.2 V, Nominal Capacity 35 Wh. Operating Time: "> 11 hours, typical". Charge Time via USB: "6 hours : 30 minutes typical when powered off; 8 hours typical when powered on".”
Nothing here states that any of these devices is compatible with any switch. No manufacturer has tested this microphone against that chassis and published the result; the strongest statement available is that both sides’ published capabilities are consistent, which is what the named-switch check above reports and is not an endorsement. The device ceilings quoted are IEEE PD-side figures — what the device is guaranteed to receive — and the headroom beside each one is derived from them, not published by the manufacturer.
Operationally sensible ecosystem
Brands grouped by engineering role — not random logos.
Network backbone
Core switching + routing + firewall
- HPE Aruba 6100L2 managed PoE+ for mid-market
- Cisco Catalyst 1300L2 managed PoE+ alternative
- FortiGateMid-market UTM firewall
Wi-Fi access
High-density Wi-Fi 6E / Wi-Fi 7
- HPE Aruba 530Wi-Fi 6E for enterprises
- Cisco Catalyst 9120Wi-Fi 6E with controller
IP cameras
Cameras + analytics edge
- Hanwha WisenetKorean enterprise vendor
- Bosch IPEuropean optics + analytics
- Hikvision ProMid-tier Hikvision product line
· Starting configurations
Typology presets — pick a scenario, see the calculator.
Each preset opens a curated configuration page with the engineering reasoning behind the numbers. Then the calculator loads with the same inputs — change them and the URL stays shareable.
· Engineering advisory · PoE Budget Calculator
What the wattage budget predicts about the network.
The recommended switch tier is the brief-stage budget. The deployment requires the cable-length derating, the day-two refresh discipline and the operational consequence below.
01 · Deployment observations
Deployment observations
The observations4 notes — engineering detail behind this section
- Switch advertised PoE budget is the shared pool across all ports, not the per-port allocation. A 48-port PoE+ switch with a 740 W budget cannot deliver 30 W on every port simultaneously — at full load, ports beyond the budget power-cycle rather than negotiate down.
- Port count is a constraint of its own and it binds first on low-draw estates. Sensors, readers, fixed cameras and handsets draw so little that the pool is never the limit — the number of powered ports is, and on an 802.3bt chassis the count that matters is the count at the class the estate needs, which is lower than the chassis port count. The switch quantity is the larger of the power-derived and the port-derived number, never the power one alone.
- Type 3 (60 W cable / 51 W device) is the floor for Wi-Fi 7 APs, large 1080p PTZ cameras with heaters and most AV-over-IP encoders; Type 4 (90 W / 71.3 W) is reserved for video-bar systems and large heated outdoor cameras. Most enterprise networks today are predominantly Type 3, and the Type 4 budget is reserved at the rack head-end.
- Cable-length losses are real beyond 60 m runs — Cat6A holds 100 m at full PoE++ budget, Cat6 derates ~5% near the limit. The 30% spare absorbs both the device growth and the cable-length derating.
02 · Redundancy posture
Redundancy posture
Read the redundancy posture2 notes — engineering detail behind this section
- PoE switch failure pulls every powered device offline — cameras, APs, phones, intercoms all dark simultaneously. Stacked-switch architecture (Cisco IOS-XE / Aruba VSF) shares the PoE budget across the stack and tolerates a single-switch event without losing every device on that switch.
- Switch PSU redundancy (dual-PSU class) holds the PoE budget through a single PSU failure; without it, a PSU event drops half the PoE budget on a single-PSU class switch and triggers cascade port-shutdown.
03 · Environmental considerations
Environmental considerations
Read the environmental considerations2 notes — engineering detail behind this section
- Switch thermal load grows with the active PoE budget — a fully-loaded PoE++ switch dissipates 200-400 W of heat at the rack, which is the dominant rack-AC load on a typical IT cabinet. Rack ventilation is sized against the active PoE budget, not the data-only load.
- Outdoor PTZ cameras with heaters can draw 30 W in winter and 14 W in summer — the budget must hold the winter peak, not the summer baseline. Per-camera draw varies with ambient temperature and operating mode.
04 · Commissioning discipline
Commissioning discipline
Read the commissioning discipline3 notes — engineering detail behind this section
- Link-budget test on every PoE run at handover — per-port PoE class negotiation, per-port wattage delivery verification under the actual device load, signed off in the as-built rack-and-port schedule.
- Per-port PoE class assignment documented at handover — not every port runs every device class; assignment to the right port matters for budget planning and for cable-length derating discipline.
- Configuration baseline export for the switch stack — port descriptions, VLAN assignment, PoE class assignment and stack member identity stored offline for clean-slate recovery within the same business day.
05 · Lifecycle implications
Lifecycle implications
Read the lifecycle implications2 notes — engineering detail behind this section
- Switch chassis carries an 8-10 year service envelope under enterprise duty; the PoE budget envelope grows generationally — Wi-Fi 6 to Wi-Fi 7 typically grows per-AP draw by 30-50%, which is what the 30% spare absorbs across a typical 5-year refresh.
- Per-port PoE chip wear is not a documented service-life signal but is the leading silent failure mode on heavily-loaded ports — replacement is a like-for-like switch swap, not a chip-level repair.
06 · Expansion readiness
Expansion readiness
Read the expansion readiness2 notes — engineering detail behind this section
- Port count expansion typically lives in the existing stack capacity until the stack is full; beyond that, a new stack member or a parallel stack is the minimum incremental scope.
- Generational PoE-class upgrade (PoE+ → PoE++ Type 3) is a switch refresh — the cable plant carries the higher class without re-cabling, but the switch chassis must support the new class.
Verification status: Conditional engineering model — assumptions stated · Adversarially verified and regression-guarded · reviewed 2026-08-30
· Engineering notes
How to read this tool’s output
Stage 3 (design) or stage 4 (BOQ). Use during switch-sizing to validate the PoE class and SKU.
The assumptions, limits and reference architectures behind this
What an engineer should know
The assumptions behind the numbers this tool produces.
- PoE-powered device counts in — total watts, switch tier (PoE+ / PoE++ Type 3 / Type 4) and indicative SKU band out.
- 30% headroom is built in and is not adjustable in the tool — it is sized for a five-year refresh. A genuinely static device count needs less than that, which is a judgement for the design review rather than a slider.
When this tool is the right one
The project moments and room types this is built for.
- IT lead sizing the switch class for a Wi-Fi 7 + IP surveillance refresh.
What changes the answer in practice
Field conditions that move the result away from the planning figure.
- Type 4 (90 W) PoE++ powers small displays and high-end APs, but cable plant must be Cat6A end-to-end.
Defensible starting architectures
Vendor-neutral reference points, not a recommendation to buy — the right answer is the one that survives your site survey.
- PoE++ Type 3 backbone for standard deployments; Type 4 reserved for devices that need the headroom.
Common mistakes
Failure patterns we see on real projects.
- Treating PoE class as flat across device families — IR-illuminated cameras spike the actual draw.
How this lands against adjacent systems
What else has to be agreed before this output is safe to build to.
- Pairs with the Network Calculator for the year-three switch and AP count.
Where this tool fits
The building types this output is calibrated for — and, where we have said so, the ones it is not.
Best suited for
Not the tool to reach for
The standards and technologies this touches
Reference pages for the protocols, standards and systems behind this tool’s output.
· Why budget right matters
A 48-port switch advertised as PoE+ does not deliver 30 W on every port. The budget is a shared pool: 740 W split across 48 Wi-Fi 6 APs at 18 W expected draw comes to 864 W — over the pool by 124 W, which means some APs power-cycle under load. The opposite failure is just as common: 60 occupancy sensors fit that pool several times over and still do not fit the 48 powered ports. Every figure in those sentences is read out of this tool's own device table and switch ladder. Sizing against the actual device draw and the port count at design time, with 30% spare, is the difference between a network that runs and one that visits the rack at 3 a.m.
· Frequently asked
PoE Budget —
what people ask first.
What is a PoE budget?
A switch's PoE budget is the total watts it can deliver to powered devices across all ports combined. A 24-port PoE+ switch with a 370 W budget cannot supply 30 W on every port simultaneously — only about 12 ports can be fully loaded. The pool is not the only limit: that same chassis terminates 24 powered devices whatever they draw. Sizing against actual device draw plus headroom, and against the powered-port count, is the correct planning method.
Does the number of ports matter as well as the wattage?
Yes, and on low-draw estates it is the binding constraint. Power and ports are independent: a 24-port chassis with a 370 W pool has the wattage for dozens of 4-6 W sensors and the ports for 24 of them. On an 802.3bt chassis there is a third number — the ports capable of the class the estate needs, which is smaller than the chassis port count, because the heavier classes are offered on a subset of the ports. The right switch quantity is the larger of the power-derived and the port-derived figure. The calculator above floors on all three and states how many chassis the estate takes.
Can I budget a specific camera model rather than a category?
Yes. 343 camera models can be named in the calculator, and 305 of those carry the manufacturer's own published maximum draw. Naming one budgets the camera row at that figure instead of the expected figure for the family, and because the published draw also decides the IEEE class, it moves the per-port class floor and the powered-port count as well as the pool. The remaining 38 publish no maximum draw at all; they can still be named, the row stays at the family's expected figure, and the tool states that the wattage is an assumption rather than filling it in. Across the whole catalogue 49 of 356 profiles publish no maximum draw — an unknown we publish as an unknown.
What about conference microphones and DSP on the same switch?
They belong in the same budget and this table has no row for them, so the page lists them instead of guessing. 13 of 19 conference-audio records publish both a maximum draw and an IEEE family — 11 state that 802.3af is sufficient and 2 state a heavier family — and each one is listed on this page with the manufacturer's own wording and where it was read. Budgeting them on the nearest family row instead, the av-over-ip node at 18 W, reserves 234 W for one of each against a published 141.45 W, and asks for a heavier port class than 11 of them need. The other 6 records publish no maximum draw at all — a typical or approximate figure is not a maximum — so they carry no wattage here rather than a manufactured one. Note that 2 of the listed devices sit within a watt of the device-side ceiling of the class they declare, which is the margin a long channel eats.
When do I need PoE++ Type 3 vs Type 4?
Type 3 (60 W cable / 51 W device) is needed for Wi-Fi 7 APs, large 1080p PTZ cameras with heater, small kiosk displays and some AV-over-IP encoders. Type 4 (90 W / 71.3 W) is reserved for video-bar systems, large pan-tilt-zoom-heated outdoor cameras, and powered displays up to 12 inches. Most enterprise networks today are predominantly Type 3.
Why 30% headroom?
Five-year refresh cycles see device counts grow ~6% per year and per-device draw increase as Wi-Fi standards advance. A 30% spare keeps the switch in budget over the cycle without forcing an early replacement. Beyond 30%, the cost premium of an over-sized switch tier is rarely justified. The figure is fixed in the tool — there is no control to change it, and the page no longer suggests otherwise.
Does the tool account for cable-length losses?
It uses the device-side wattage (after PSE-to-PD efficiency losses). For runs near the 100 m limit, derate the device draw by ~5% as a conservative buffer. Most premium installs land at 30–60 m runs where loss is negligible.
Will TechnoGuru spec the switch and install it?
Yes. Enterprise switching, structured cabling and PoE network design are core services. We specify Cisco, HPE Aruba and Juniper enterprise classes, with NETGEAR M-class as a value-tier alternative for SMB. End-to-end commissioning with link-budget testing on every PoE run.
Engineering toolkit
Next in this sequence
Calculators whose inputs or outputs connect to this one.
- IT · Networking
Network & PoE Calculator
Sized to year-three load — switches, Wi-Fi 7 access points, PoE budget (watts), Cat6A run count, port/AP sizing. Cisco / HPE Aruba / Juniper-class enterprise gear.
Switches · APs · PoE WOpen - IT · Wi-Fi · Coverage
Wi-Fi AP Planner
Floor area, ceiling height, wall material and client density in — AP count, PoE budget, switch ports and channel-plan advice out. Wi-Fi 6 / 6E / 7 with material-derated coverage and hex-packed cell preview.
APs · PoE · channelsOpen - IT · Cabling
Structured Cabling Estimator
Estimate total structured-cabling length, patch panel count and IDF closet count against floor area and drop count. 50 cable-system brands including Panduit, CommScope, Belden, Legrand, Corning, Furukawa, R&M, Siemon, Nexans, Schneider Electric, STL, Finolex and Polycab. Cat6, Cat6A, Cat7, Cat8 copper plus OM3, OM4, OS2 fibre. TIA-568 compliant.
50 brands · 7 categoriesOpen
· Begin
Planning a PoE network
for a large building?
Send the BOQ of PoE devices, building floor plate and cable routing intent. We will return a switch BOM with PoE budget headroom and rack elevation within two working days.