SmartPole OS

// IMPACT_STATS

7 TYPES

Classes supported
CCTV·EV Charger·Luminaire·Environmental Sensor·SOS Terminal·Digital Signage·IP Public Address

Dual-Path

Network redundancy architecture
Supports fiber + 4G/5G active-passive configuration

6 MODULES

Active from day one
No staged rollout, no per-module licensing

90 DAYS

Maximum go-live commitment
Written into the deployment contract

// OVERVIEW

Every Protocol.
One Central Command.

Today, every device on a smart pole — the luminaire controller, the environmental sensor, the EV charger, the CCTV unit — speaks a different protocol and reports to a different vendor portal. MQTT from your sensors. OCPP from your chargers. ONVIF from your cameras. Three logins. Three maintenance workflows. No cross-device automation.

SmartPole OS terminates all of that at the server. A single middleware engine normalises incoming data from every protocol — MQTT, LoRaWAN, OCPP 1.6/2.0.1, Modbus, ONVIF — into a unified data layer. From there, a central rules engine handles cross-device automation, alert routing, predictive scoring, and compliance reporting. The dashboard is how operators see and control that layer. The middleware is what makes it possible.

View Live Demo See All Modules

// The Integration Problem

Each device vendor ships its own portal — lighting, EV, CCTV, and sensors never share a data layer

No cross-device automation — a flood alert cannot trigger a lighting profile change or emergency PA broadcast without custom middleware

Fault detection is reactive — operators learn about failures from field reports, not from the platform

No unified audit trail — compliance, billing, and council reporting must be assembled manually from fragmented vendor exports

Every new hardware variant requires a fresh integration project, even when the sensor category already exists

// CORE_MODULES

Six Modules. One Middleware Stack.

All six modules are active from day one — no staged rollout, no per-module licensing. Every inference, every automation rule, every alert runs at the server layer.

MODULE_01

Energy & EV Management

Ask About This

Server-hosted management of luminaire networks and EV charging infrastructure from a single operator console. Luminaire control operates via NEMA-7 or DALI-compatible controller networks, with astronomical clock-based scheduling and per-luminaire fault detection pushed down as commands from the central host. EV charger management uses OCPP 1.6 and OCPP 2.0.1 for open-standard communication — no vendor lock-in, no proprietary charge network dependency. Charging transactions are logged centrally with export support for LHDN MyInvois e-invoicing compliance. Payment gateway integration (TnG eWallet, GrabPay) support are available.

EV Uptime

kWh Tracking

Lamp Dimming

Zone Reports

MODULE_02

Flood & Emergency Alerting

Ask About This

Server-side ingestion of water level and rainfall intensity telemetry from field sensor nodes via the Favoriot IoT platform MQTT bridge. Configurable alert thresholds per sensor node and geographic zone trigger automated SMS and push notification cascades to operations wardens and emergency response teams. Cross-module rule engine integration allows flood alerts to automatically override signage content and activate PA emergency broadcasts without manual operator intervention.

Water Level

Rainfall

SMS Alert

Thresholds

Geo Zones

MODULE_03

Predictive Maintenance

Ask About This

Server-side health scoring model applied continuously to per-unit telemetry — consumption patterns, current draw, data connectivity — to generate 7-day fault likelihood scores with 85%+ prediction accuracy on monitored failure modes. When a unit crosses a configurable risk threshold, the platform automatically generates a maintenance task and routes it to the assigned field team. No additional instrumentation required — the platform derives predictive signals from existing telemetry streams already flowing through the middleware layer.

ML Health Score

Maint. Queue

Fault Predict

Field Routing

7-Day Window

MODULE_04

AI Vision Engine

Ask About This

Multi-stream video analytics running entirely on the central server host — no edge compute hardware required at the pole. Standard IP cameras connect via ONVIF or direct RTSP stream; the platform handles all inference server-side. Available analytics sub-modules include people flow counting, Automatic Number Plate Recognition (ANPR), crowd density monitoring, and stationary object / incident detection. For standard deployment scales, inference runs on general-purpose server CPU without dedicated GPU infrastructure. Facial recognition functionality is disabled by default and requires written authorisation prior to activation, consistent with the explicit consent requirement for sensitive personal data under PDPA Section 40 (as amended by the Personal Data Protection (Amendment) Act 2024).

People Count

ANPR

Incident Detect

Plate Read

PDPA Gated

MODULE_05

Environmental Sensing

Ask About This

Real-time ingestion and centralised parsing of environmental sensor telemetry via the Favoriot IoT MQTT bridge. Monitored parameters include PM2.5, PM10, CO₂, NO₂, temperature, humidity, rainfall intensity, wind speed, and UV index — dependent on sensor hardware deployed at the pole. Rolling trend windows and configurable threshold alerts allow operators to trigger automated responses (signage content, PA alerts, operational notifications) when air quality or environmental parameters breach defined limits. Monthly reporting exports are structured in alignment with SSAP 2025 air quality and mobility KPI requirements for council submission.

Temperature

Humidity

Wind Speed

CO₂ & UV

PM2.5

MODULE_06

Digital Signage & PA

Ask About This

Centralised playlist and content management for pole-mounted LED signage panels, with proof-of-play logging for media owner revenue auditing and concession verification. Emergency broadcast override — triggered manually by operators or automatically by the cross-module rules engine — instantly replaces scheduled content with priority messaging across targeted zones. IP Public Address system management supports scheduled civic announcements and real-time emergency audio broadcasts. All content changes, overrides, and scheduling events are written to the central audit trail with timestamp and operator attribution.

LED Panels

Proof of Play

PA Broadcast

Scheduling

Zone Target

// SYSTEM_ARCHITECTURE

Four Layers. Every Protocol Normalised.

SmartPole OS sits across your infrastructure as a middleware layer — not replacing what you have, but normalising, routing, and securing every data stream through a central processing core.

Platform & Insights Unified Dashboard & Actionable Orchestration

Energy & EV Load Balancing

Disaster Flood / Early Warning

Predictive Maintenance AI

AI Vision Traffic & Crowd

Environment AQI & Noise

Signage & PA Civic Broadcast

SmartPole OS Core Data Ingestion, Central Processing & Security Compliance

Data Normalisation Protocol-agnostic ingestion layer

Server-Side AI Analytics Central inference, no pole-level compute

PDPA Anonymisation Zero PII export

Rules Engine MCMC-compliant threshold logic

Encrypted Network Layer 5G / 4G LTE · LoRaWAN (Class A/C) · Fiber · AES-256

5G / Fiber Dual-Path Failover < 30 s · Active-Passive

LoRaWAN (Class A/C) Low-power wide-area sensor network

AES-256 Transport End-to-end encrypted · NACSA

Favoriot API Bridge MQTT broker cluster · QoS 2

Device Edge Agnostic Hardware Integration & Sensory Nodes

Smart Lighting CCTV Arrays EV Terminals IoT Sensors

// HOW_IT_WORKS

From Pole to Dashboard in Four Steps.

01

Connect

Any vendor hardware. Any protocol. Onboarded via native integration.

02

Stream

Telemetry transits to the central server over dual-path, with automatic failover.

03

Process

The middleware normalises every data stream into a unified schema.

04

Operate

One console. Live device status and council-ready exports — no vendor portals.

// DEPLOYMENT_SCENARIOS

Built for Campus. Highway. City Precinct.

SmartPole OS scales from a 50-pole university campus to a 2,000-pole municipal highway network. The same platform, the same dashboard, the same SLA.

University & Corporate Campus

A managed campus network where student and staff safety, energy consumption, and EV charging revenue all run from one operations centre. Lighting adjusts automatically to occupancy, flood sensors feed into the facilities management workflow, and the EV charging fleet reconciles to the finance system daily.

Security incidents detected by the AI Vision Engine trigger automatic PA announcements and notify the campus security team — no manual handoff required.

Map SmartPole OS to Your Campus

50–500 Poles per campus deployment
Typical university or corporate park scale

40% Reduction in incident response time
Via automated alert routing and PA integration

90 DAY Go-live commitment
Written into the deployment contract

Highway & Expressway Corridor

A high-density linear deployment where pole health, lighting levels, and incident detection must be monitored continuously across hundreds of kilometres. Predictive maintenance prevents lamp failures before they create dark zones, and ANPR data is logged centrally and can be exported or API-integrated with traffic authority reporting systems.

Environmental sensors along the corridor feed into the national air quality network, satisfying SSAP 2025 reporting requirements without additional instrumentation.

See the Highway Deployment Spec

500–2000 Poles per highway corridor
Typical expressway or federal road scale

85%+ Fault prediction accuracy
7-day horizon via ML health scoring

<30s Network failover time
Dual-path fiber / 5G redundancy

Municipal City Precinct

A council-managed urban precinct where SmartPole OS serves as the central operations layer — connecting lighting, CCTV, environmental monitoring, digital signage, and flood alerting under one roof. Council reporting exports automatically on a monthly schedule, and all data resides in-country under PDPA data residency requirements.

Multi-tenant isolation means a single SmartPole OS instance can serve multiple councils or precincts, each with their own dashboard view and their own data boundary.

Request a Precinct Scoping Report

Multi Tenant support
Multiple councils, one platform instance

Monthly Automated council reporting
SSAP 2025 KPI export, zero manual effort

PDPA In-country data residency
No data leaves Malaysian jurisdiction

// TECHNICAL_SPECIFICATIONS

Under the Hood.

Runtime

Python-based platform. Containerised deployment (Docker / Kubernetes). Linux host OS.

Device Protocols

MQTT v3.1.1 / v5.0 · LoRaWAN (Class A/C) · OCPP 1.6 / 2.0.1 (EV charging) · ONVIF (CCTV) · Modbus RTU / TCP

Integrations

Favoriot IoT Platform (MQTT broker) · MyInvois (LHDN e-invoicing) · Payment gateway support: TnG eWallet, GrabPay (subject to merchant agreement) · SSAP 2025-aligned reporting exports · SMS gateway (Twilio or local Malaysian provider)

APIs

REST (JSON) · WebSocket · Webhook · AsyncAPI Spec Published

Data Sovereignty

All data stored within Malaysian jurisdiction. PDPA residency requirements enforced at the platform layer. No third-party data sharing without explicit written consent.

Uptime SLA

High-availability deployment architecture with dual-path network failover under 30 seconds. Platform uptime commitments are defined per deployment based on hosting configuration and are specified in the service agreement.

Security

AES-256 encryption at rest and in transit · NACSA-aligned audit logging · Role-based access control (RBAC) · SOS priority queue with guaranteed 3-second dispatch

Scale

Tested to 2,000+ poles per tenant. Multi-tenant architecture with full data isolation between tenants. Horizontal scaling via container orchestration.

// COMPLIANCE

Built-In. No Procurement Surprises.

SmartPole OS ships PDPA-compliant, MCMC-ready, and Madani-aligned. The table below shows exactly what we handle versus what stays with you.

Requirement	Standard	Handled By Platform	Deployer Responsibility
Personal data storage	PDPA	In-country residency enforced, AES-256 at rest	Data collection consent notices at point of capture
Telecommunications licensing	MCMC CMA 1998	Platform designed to operate within licensed network infrastructure; TTD does not hold or require an MCMC licence to supply the platform	Operator holds applicable MCMC class licence
Facial recognition activation	PDPA s.40 · Ethics	Module disabled by default, gate enforced	Written approval required before activation per deployment
Air quality KPI reporting	SSAP 2025	Automated monthly export to council endpoints	Submission sign-off by appointed council officer
e-Invoice fiscal compliance	LHDN MyInvois	EV charging transactions auto-linked to MyInvois	Deployer holds SST registration if applicable
Cybersecurity incident logging	NACSA	Tamper-evident audit log, 24-month retention	Incident reporting to CyberSecurity Malaysia if threshold met
EV charger interoperability	OCPP 1.6 / 2.0.1	Open-standard OCPP supported, no vendor lock-in	Charger hardware must carry SIRIM certification

// DEPLOYMENT_CONFIGURATOR

Know Your Zone ?

Three steps. One scoping brief — pre-filled, procurement-ready, and waiting in your inbox.

01 Zone

02 Scale

03 On-Site

Where is your deployment?

How many poles are you planning?

What's already on site? (optional — select all that apply)

Skip — take me straight to the form

// ALSO_SEE

Every Protocol. One Central Command.

Six Modules. One Middleware Stack.

Four Layers. Every Protocol Normalised.

From Pole to Dashboard in Four Steps.

Built for Campus. Highway. City Precinct.

University & Corporate Campus

Highway & Expressway Corridor

Municipal City Precinct

Under the Hood.

Built-In. No Procurement Surprises.

Know Your Zone ?

Every Protocol.
One Central Command.