What is the difference between NEMA-socket and embedded lighting controls?

NEMA-socket controllers plug into the standard 3-, 5-, or 7-pin socket on top of a streetlight fixture (retrofit-friendly). Embedded controllers are integrated directly into the fixture during manufacturing, reducing labor and failure points for new installations. A good vendor supports both.

Should smart lighting support FedRamp, StateRamp, or DoD deployments?

For any deployment on or near federal infrastructure, yes. Vendors should support StateRamp, FedRamp, or GovCloud equivalent — and should have at least one demonstrated DoD deployment reference. This proves the vendor can navigate the highest-scrutiny procurement environments.

What surge protection level is required for outdoor lighting controls?

A minimum of 20kV/10kA surge protection. Outdoor lighting is repeatedly exposed to lightning, transient overvoltage, and weather-driven surges — anything less exposes the deployment to preventable failures during storms.

How much install base experience should a smart lighting vendor have?

At minimum, 125,000 wireless lighting controls deployed with a demonstrated failure rate below 1%. Plus at least three deployments greater than 75,000 controls — proving they can manage data and assets at citywide scale, not just pilot scale.

Wireless Outdoor Lighting Control RFP Guidelines

Q: Why does the RFP need to specify tilt measurement?

Tilt sensors detect creeping pole lean, damage from vehicle strikes, or downed poles. Setting an alarm at a specific angle enables proactive maintenance and rapid response to storm-damaged infrastructure — critical for safety on urban and highway lighting.

Q: What fixture types should a smart lighting controller support?

It should interface with LED, CF (compact fluorescent), HID (high-intensity discharge), and HPS (high-pressure sodium) fixtures. Cities typically have mixed inventories from different installation eras, and a single controller across fixture types simplifies procurement, spares, and training.

Q: What metering accuracy should a smart lighting controller have?

ANSI C12.20-compliant metering with accuracy at 0.5% or better. This utility-grade standard is essential for balancing the grid, accurately reporting energy consumption for reimbursement, and validating billing against the utility.

Q: What is FIPS 140-3 and why does it apply to smart lighting?

FIPS 140-3 is a US federal encryption certification. Requiring FIPS 140-3-compliant encryption (or the AES-256 / ECC equivalents) protects data in transit and at rest, and is often mandatory for deployments on federal sites or in security-sensitive jurisdictions.

Q: What is upstream power quality monitoring for streetlights?

The controller's ability to differentiate power problems in the grid (upstream) from problems in the light fixture (downstream). Without upstream monitoring, every dark light triggers a diagnostic truck roll. With it, crews know before dispatch whether the issue is the grid or the fixture.

Q: Should smart lighting vendors be ISO 27001 certified?

Yes. ISO 27001 certifies that the vendor operates a documented Information Security Management System (ISMS) with regular external audits. For smart city infrastructure connected to municipal networks, this baseline is non-negotiable.

Q: What warranty length is typical for smart lighting controllers?

Ten years plus 120 days from date of receipt, covering defects due to design, performance, workmanship, or materials. The warranty should specify full-unit replacement — not just defective components — to protect the city's installation investment.

Q: Is SOC 2 compliance required for smart lighting cloud infrastructure?

SOC 2 compliance is the emerging standard for cloud infrastructure handling utility data. Supply-chain risk assessments increasingly require it, and vendors without SOC 2 attestation should be considered higher-risk for procurement.

The specifications, standards, and vendor requirements municipalities and engineering firms should evaluate when writing RFPs for smart streetlight control systems.

Smart streetlight controllers are the foundation of connected city lighting — enabling remote dimming, real-time diagnostics, energy analytics, and multi-application infrastructure. Choosing the right one starts with an RFP that specifies the standards, reliability benchmarks, and security controls a municipal-grade solution actually needs.

This guide distills the most important specifications from thousands of RFPs Ubicquia has evaluated over the years. Use it as a starting point for your own requirements — the categories below cover fixture compatibility, reliability standards, cybersecurity, and the deployment-scale evidence that separates proven vendors from unproven ones.

The RFP guide, by the numbers

35+

Critical specifications covered in this guide

125K+

Install-base benchmark for proven-scale reliability

Frequently asked specification questions

Why does the RFP need to specify tilt measurement?

What fixture types should a smart lighting controller support?

What metering accuracy should a smart lighting controller have?

What is FIPS 140-3 and why does it apply to smart lighting?

What is upstream power quality monitoring for streetlights?

Should smart lighting vendors be ISO 27001 certified?

What warranty length is typical for smart lighting controllers?

Is SOC 2 compliance required for smart lighting cloud infrastructure?

How to use this guide

Every project has different priorities — a rural municipality has different security exposure than a federal installation; a small pilot has different scale demands than a citywide retrofit. Treat these specifications as a menu, not a checklist. The categories below are ordered by the frequency they appear as make-or-break criteria in municipal RFPs Ubicquia has responded to.

If you're preparing an RFP and want to discuss which specifications apply to your project, Ubicquia's field engineering team is available for a working session — no obligation.