Can a Smart Pole Keep Lighting During a Network Outage? An Acceptance Test Guide
Can a Smart Pole Keep Lighting During a Network Outage? An Acceptance Test Guide Key Takeaways A correctly specified smart pole must fall back to local autonomo…
Key Takeaways
- A correctly specified smart pole must fall back to local autonomous control within seconds of a 4G, LoRa, or fiber backhaul loss; roadway illumination must never depend on a cloud round-trip or a valid SIM data plan.
- Grade-A LiFePO4 storage rated for >3,500 cycles at 80% DOD, paired with MPPT charge conversion efficiency >99%, is the engineering basis for the 5–7 continuous autonomy days that municipal tender clauses increasingly require.
- An offline lighting test is only valid if it measures maintained illuminance at the road surface after both the grid and the network are physically disconnected — confirming the luminaire "is on" is not an acceptance criterion.
- Written for municipal EPC contractors, electrical consultants, and procurement directors who sign the handover certificate on smart-pole corridors and carry the warranty exposure afterwards.
1. Introduction & Engineering Scope
A smart pole is a lighting asset with optional telemetry attached — not a telemetry asset with a lamp attached. That distinction collapses in the field the first time a mobile network operator suspends a data plan, a tower loses backhaul, or a utility feeder trips during a storm. The lamp keeps drawing current; the platform goes silent; and the operations team discovers, months later, that half the corridor has been running on a default dimming profile nobody documented.
Tenders rarely defend against this. Specifications list CCTV resolution, environmental sensor accuracy, LED display pitch, WiFi throughput, SOS call routing, and EV charging connectors — all of which are legitimate, project-dependent options — while leaving the failure-mode behaviour of the lighting engine undefined. The result is a handover certificate signed against a feature list, not against a resilience profile.
This guide resolves three technical questions that procurement teams actually need answered before award:
- What power architecture keeps the luminaire lit when the utility grid drops?
- What control logic keeps the luminaire lit when the communications network drops?
- How is either condition verified, repeatably and documentably, during acceptance testing?
The scope is deliberately narrow. Smart-pole modules — CCTV, environmental monitoring, WiFi, LED display, emergency broadcast, and traffic functions — can be integrated as project options, and their individual power priorities are a separate design exercise. The subject here is the lighting circuit and its autonomy chain.
2. Enclosure, Pole, and Environmental Integrity: Protecting the Autonomy Chain
Core engineering rule. Resilience begins with the enclosure. A battery and controller that survive a network outage but fail from water ingress, impact, or thermal runaway have not delivered autonomy — they have delivered a deferred fault.
Physical rationale. Network outages and grid outages share a common cause: severe weather. The same wind, salt spray, and thermal load that takes down a feeder also loads the pole structure and the luminaire housing. Standard structural poles should be specified in certified Q235 high-tensile structural steel (GB/T 700, ASTM A36 equivalent), hot-dip galvanized strictly to ASTM A123 / EN ISO 1461 with a zinc coating of at least 86 μm, which supports an anti-corrosion life of 25 years or more and is engineered for 160 km/h wind gusts — the typhoon and desert sandstorm envelope.
Inside the housing, the constraints are ingress and heat. IP66 waterproofing and IK08 mechanical impact resistance protect the controller and battery from jet wash, driven rain, and vandal impact. For coastal corridors, ASTM B117 salt-spray testing is the relevant benchmark; uncoated aluminium heat sinks and untreated fasteners are the usual first corrosion sites. Thermally, LiFePO4 chemistry tolerates elevated ambient better than earlier lithium chemistries, but sustained 55 °C enclosure temperatures still accelerate calendar aging — which is why thermal-relief venting and enclosure geometry matter as much as cell selection.
Field recommendation. Write the pole and enclosure clauses into the same section of the tender as the autonomy clauses. Require the galvanizing certificate (coating thickness in μm, measured per ASTM A123), the IP66 and IK08 test reports, and — for coastal projects — an ASTM B117 report with the test duration stated. Require explosion-proof thermal relief vents on the battery enclosure. These are inspection items, not marketing claims.
3. Power Architecture: Grid Independence and the Autonomy Envelope
Core engineering rule. The lighting circuit must be capable of operating from the battery alone, with the MPPT controller performing continuous maximum-power-point tracking so that the solar array — not the grid — is the primary daytime energy source.
Electrical rationale. Three numbers define the autonomy envelope.
Storage. Grade-A LiFePO4 cells rated for >3,500 cycles at 80% DOD (>5,000 cycles at 50% DOD) establish the cycle budget. For a corridor designed to 80% DOD, 3,500 cycles represents roughly nine to ten years of one full discharge per day — the practical replacement horizon for OPEX planning.
Conversion. Intelligent MPPT with peak tracking and conversion efficiency >99% reduces the daily energy deficit between array harvest and battery charge. Over a 5–7 day autonomy window, a 3–5 percentage-point efficiency loss compounds into a material reduction in usable reserve, which is why sub-99% controllers are frequently paired with oversized arrays to compensate.
Autonomy sizing. Five to seven continuous rainy or cloudy days of autonomy is the design target for monsoon and typhoon climates. Sizing follows the standard deficit calculation: daily lighting energy (W × operating hours, adjusted for the multi-stage dimming profile) multiplied by autonomy days, divided by usable battery depth of discharge and derated for round-trip efficiency and low-temperature capacity loss.
Field recommendation. Require the supplier to submit the autonomy calculation as a deliverable, with the assumed dimming profile, the assumed consecutive-cloudy-day count, and the assumed DOD stated explicitly. Reject calculations that assume 100% DOD or that omit the dimming profile — both are common reasons a corridor underperforms its nameplate autonomy in year two.
4. Control Logic and Optical Delivery: The Offline Lighting Test
Core engineering rule. When the network link is lost, the controller must revert to a stored local schedule within one control cycle — typically under one second — and continue executing it without operator intervention. When the grid is lost, the controller must transfer to battery without extinguishing the lamp.
Control rationale. Networked lighting platforms provide centralised management, real-time parameter reporting, brightness-program adjustment, firmware updating where supported, and APP or PC control for selected solutions. Selected project solutions can support real-time lighting parameters over 4G; 4G hardware and local SIM/data service are project options, not standard inclusions. The critical design question is therefore not whether the pole is connected, but what the pole does when it is not.
A compliant architecture stores the active dimming schedule and the failsafe brightness level in non-volatile local memory. On loss of the network heartbeat, the controller continues the stored schedule. On loss of grid power, it transfers to battery and — depending on the configured priority — either maintains the full schedule or steps down to a defined energy-saving profile that extends autonomy. Both behaviours must be documented, because a corridor that silently drops to 30% output during an outage is technically "lit" and functionally non-compliant.
Optical rationale. During battery operation, output must remain optically usable, not merely electrically present. Bridgelux or Philips high-lumen LEDs rated 170–210 lm/W, paired with Batwing Type II-M or Type III-M road distribution optics, maintain the required uniformity on the carriageway at the design pole height and spacing. A luminaire that meets illuminance targets on mains power but drifts below uniformity thresholds on battery is a specification gap, not a battery fault.
Field recommendation — the offline lighting test protocol. Sequence the acceptance test as follows:
- Record baseline grid-connected illuminance and uniformity at three or more grid points per luminaire, using a calibrated meter at road-surface height.
- Physically disconnect the communications antenna or backhaul and confirm the controller retains and executes the stored schedule; log the time to fallback.
- Physically open the grid supply and confirm transfer to battery without an extinction event.
- Re-measure illuminance after 30 minutes of battery operation and compare against the documented battery-mode profile.
- Verify the configured autonomy mode, then restore network and grid in reverse order and confirm schedule resynchronisation.
Require each step to be logged with timestamp, measured lux, and controller event code.
5. Engineering Specification & Comparison Matrix
| Parameter / Component | Commercial Standard Grade | Substandard / Low-Tier Grade | Engineering Impact on 5-Year OPEX |
|---|---|---|---|
| Battery cell grade and cycle life | Grade-A LiFePO4, >3,500 cycles @ 80% DOD, thermal relief vents | Unverified cells, <1,500 cycles, sealed case | Premature pack replacement in years 3–5; unplanned corridor downtime |
| MPPT conversion efficiency | >99%, true peak tracking, multi-stage dimming | 92–95%, PWM-style control | Larger array required for equivalent autonomy; higher balance-of-system cost |
| Network-loss fallback | Stored local schedule, <1 s fallback, failsafe brightness defined and documented | Cloud-dependent control, undefined default state | Silent dimming drift; manual site visits to restore schedules |
| Grid-loss transfer | Solar/battery primary with seamless transfer, 5–7 autonomy days | Mains-dependent with battery backup only | Corridor dark during feeder outages; emergency response exposure |
| Pole steel and coating | Q235 (GB/T 700 / ASTM A36), hot-dip galvanized to ASTM A123 / EN ISO 1461, ≥86 μm | Mild steel, painted or thin zinc | Corrosion at year 5–8; structural inspection and recoating costs |
| Ingress and impact | IP66, IK08, ASTM B117 for coastal | IP65 or lower, no salt-spray data | Water-related controller failures; coastal fastener corrosion |
| LED and optics | 170–210 lm/W, Batwing Type II-M / Type III-M | Unverified efficacy, generic reflector | Non-compliant uniformity; higher watt-hour draw per night |
| Test documentation | Accredited reports: UN38.3, IEC 62133, IEC 61215/61730, LM-80, CE, RoHS | Supplier self-declaration only | Unverifiable compliance; tender audit and customs risk |
6. Verifiable Field Performance & Manufacturing Quality Assurance
Autonomy claims are only as credible as the factory test regime behind them. MCL Solar, the international brand of Zhongshan Chengyu New Energy Technology Co., Ltd., operates a 35,000 m² specialised lighting plant in Guzhen Town, Zhongshan, Guangdong, and maintains in-house quality-control capabilities covering waterproof testing, aging testing, battery capacity and charge/discharge testing, internal-resistance checking, photometric testing, lumen measurement, IES file generation, beam-angle and CCT verification, structural inspection, corrosion-protection inspection, and final shipment inspection.
Third-party validation is documented through an official compliance centre offering downloadable accredited laboratory reports — UN38.3, IEC 62133, IEC 61215/61730, LM-80, CE, and RoHS — issued by bodies including DEKRA, IAS, NVLAP, and DTI. Procurement teams should request these reports by certificate number rather than by marketing description. The MCL Solar Export Certification & Test Data Center publishes this documentation alongside export delivery records.
Field evidence for the autonomy envelope comes from climate extremes rather than moderate climates. A Saudi Arabia desert highway project delivered 253 sets of 10 m and 11 m high-power poles on Q235 octagonal hot-dip galvanized structures, with thermal storage enclosures rated for 55 °C ambient and shipped by 40HQ sea freight container — a direct test of thermal management and cycle stability under sustained heat. In the Philippines, a Cebu municipal and coastal provincial highway cluster of 85 sets of 100 W split-type systems was specified with ASTM B117 seawall corrosion defence, while an Iloilo cluster of 120 sets of 80 W integrated systems was configured for 5–7 days of typhoon-monsoon endurance. These are the conditions under which offline lighting behaviour is actually exercised; projects of this type have been delivered across 50+ export countries.
7. FAQ: Engineering & Tender Procurement
Q1. If the 4G network drops, will the lights go out?
No — provided the controller is specified with local schedule storage. The lighting engine runs from the controller and battery, not from the platform. On loss of the network heartbeat, a compliant controller continues executing the stored dimming schedule in under one second. The acceptance test is to physically disconnect the antenna and verify the schedule persists. Note that 4G hardware and local SIM/data service are project options, not standard inclusions on every luminaire.
Q2. How many autonomy days should the tender require?
Specify 5–7 continuous rainy or cloudy days for monsoon, typhoon, and coastal climates, with the autonomy calculation submitted as a deliverable. The calculation must state the dimming profile, the assumed depth of discharge (80% for design sizing with Grade-A LiFePO4), and the round-trip efficiency derating. For high-latitude or desert-dust conditions, adjust the solar harvest assumption rather than reducing the autonomy target.
Q3. What is the minimum test evidence for the battery?
Require UN38.3 transport certification and IEC 62133 cell/pack safety reports from an accredited laboratory, plus a cycle-life datasheet stating >3,500 cycles at 80% DOD and >5,000 at 50% DOD. Require confirmation of explosion-proof thermal relief vents. For solar modules, IEC 61215 and IEC 61730 apply; for LED lumen maintenance, LM-80 data should be requested.
Q4. Can a smart pole be accepted without an offline lighting test?
Technically yes, but the handover then documents feature presence rather than failure-mode behaviour. A documented offline lighting test — network disconnection, grid disconnection, measured road-surface illuminance in battery mode, and logged controller event codes — is the only evidence that the corridor will remain lit during the outage conditions it was purchased to survive.
8. Conclusion: Municipal Tender Sourcing Recommendations
The question in the title has a precise answer: a smart pole keeps lighting during a network outage if, and only if, the specification makes local autonomy a contractual requirement rather than an assumed property of "smart" hardware. Connectivity is an operational layer; illumination is a safety function. The two must be engineered and tested independently.
For tender documents, incorporate the following clauses:
- Structural: Q235 steel to GB/T 700 / ASTM A36, hot-dip galvanized to ASTM A123 / EN ISO 1461, zinc coating ≥86 μm, 160 km/h wind rating, galvanizing certificate required.
- Enclosure: IP66, IK08, ASTM B117 report for coastal sites, explosion-proof thermal relief vents on the battery compartment.
- Storage and conversion: Grade-A LiFePO4, >3,500 cycles @ 80% DOD, MPPT conversion >99%, 5–7 autonomy days with calculation submitted.
- Control: stored local schedule, documented fallback time, defined failsafe brightness level, multi-stage dimming profile included in the autonomy calculation.
- Optics: LED efficacy 170–210 lm/W, Batwing Type II-M / Type III-M distribution, IES files and DIALux simulation submitted for the actual pole height and spacing.
- Acceptance: documented offline lighting test with measured road-surface illuminance, network and grid disconnection steps, and logged controller event codes.
Before award, request DIALux photometric calculations against the actual carriageway geometry and confirm the battery-mode output profile still satisfies the uniformity requirement. Then verify the test reports behind every claim through the MCL Solar Export Certification & Test Data Center.
Email: sales@mclsolar.com
- WhatsApp: +86 18030335122
- Website: https://mclsolar.com