One pole, one file, lighting, charging and mounts on one screen
MeetCarbon Cloud smart poles keep a file for each comprehensive, street and landscape pole, switch and dim by group, and put energy, alarms, work orders and mounted services on one map. Charging orders settle in charging operations. This product keeps the pole-to-charger link and the overview.
- One file
- Pole, bays and mounts
- Group dimming
- Policy down to the lamp
- Alarm to ticket
- From exception to close
- Split books
- Charging, ads, sites, EMC
- Arterial group A · lamp controller offlineDispatch
- Binjiang pole 12 · dimming policy waitingDim
- EMC March settlement · waiting confirmConfirm
From a pole file to a settlement you can check
Four steps match the screens already in the product. After the pole is filed, dimming, alarms and sharing stay on that pole.
- 01
File
Enter the code, type, district, height and bays, and hang lamps, chargers, screens and sensors on this pole.
Pole file · Map - 02
Control
Switch and dim by arterial, secondary, local or landscape group. Scenes cover everyday, holiday, event and emergency full-on.
Lighting console - 03
Tickets
Offline, faults and threshold breaches become alarms. Inspection or repair tickets move from open to closed, with SLA.
Alarms · Tickets · Rules - 04
Share
Charging, advertising, site rent and EMC savings each post on their own line. Savings follow the confirmed sheet.
Energy · EMC · Sharing
What you see in smart poles
The menu groups poles and lighting, energy contracts, operations and mounts. These match the screens already in place. Open any item to see the work it does.
Map
Poles and lightingSee poles online, the share of lights on, open alarms and this month’s sharing, and open a pole or an alarm from here.
- Poles, lamps and alarms on one screen
- Districts can be opened
- Figures are samples; the ledger is the record
Pole counts, uptime, kilowatt-hours and amounts in the sample windows only show how the screen is organised.
The same pole, mounts chosen by scene
Decide what this pole has to do, then open the matching screens. These four combinations can already be registered and viewed.
The pole, dimming, energy and charger online status live here. Orders, prices and invoices live in charging operations. Roof PV covers low-voltage, communications and part of the lighting. The charger’s main supply is metered on its own.
Two-wheel charging has no menu of its own. Orders and tariffs are handled in charging operations. The pole side keeps the mount link.
Move the brightness, see the sample kilowatt-hours
One sample lamp shows the gap between dimmed and full brightness. Confirmed savings use the EMC settlement sheet.
Sample: 120 W rated, 10 hours on
The sample scales energy by brightness only. It leaves out lumen depreciation, voltage and group policy. External savings use a confirmed EMC sheet.
Dispatchers run the lamps, crews close tickets, settlement reads the sheet
The lead reads the map and whether a split is confirmed. Dispatch sends policy. Crews handle alarms and tickets. Settlement reads four income lines.
Are tonight’s lights and mount income in order?
- Poles online and lights on
- Open alarms
- Whether this month’s share is complete
The ledger, the meter and the mounts meet on one pole
Every mount has to match a pole. Charging bills are not rebuilt here. Device reads and writes go through the IoT base.
- Charging orders, prices, payment and invoices stay in charging operations.
- Protocols and thing models stay in the IoT base.
- Video pictures come from the security platform or the IoT base.
- Organisation energy hosting and building sub-meters stay in energy management.
Lighting savings and charging income on the same pole post on separate lines, so an EMC sheet and a charging share do not share a row.
File the poles and groups first, then add mounts
Do the first road in this order. Charging tariffs and IoT protocols can be prepared in parallel. The pole ledger can start first.
- 1Pole locations, codes and types
- 2Groups: arterial, secondary, local or landscape
- 3The list of lamps, chargers, screens or sensors to mount
- 4For EMC: baseline energy and contract mode
- 5Charging prices stay configured in charging operations
If the factor is missing, the carbon board has no reduction yet. You can still create poles and policy.
- 1
Create the ledger
Enter poles, districts and bays.
You getOne file per pole - 2
Connect lamp control
Put controllers in a group and confirm switch and brightness.
You getLighting console - 3
Send policy
Enable an everyday or emergency scene.
You getGroup policy - 4
Connect alarms
Offline and faults become alarms, and tickets when needed.
You getA closed loop - 5
Mount services
Link chargers, screens, sites or sensors.
You getMount ledger - 6
Settle
Confirm the EMC sheet and read the four share lines.
You getA book you can check
Assets, policy, alarms and sharing stay on one ledger
Smart poles own the pole and the mount layout. Charging operations, device access, PV monitoring, carbon assets and ESG each have their own product.
One file per pole
Type, district, height, bays and mounts sit on the same file.
Group policy
Brightness, scene and enabled state go out by road section and can be turned off.
Alarm to ticket
An open alarm can become inspection or repair, with an SLA.
Four share lines
Charging, ads, site rent and EMC savings post by party and period.
Three contracts
Shared, guaranteed and hosted each keep baseline, actual and confirm.
Mounts can be added
Lamps, chargers, screens, sites, security, environment and city services hang on the pole.
How neighbouring products connect
Poles and lighting stay here. Orders, protocols, plant monitoring, allowances and disclosure indexes go to their own products.
Roadside, retail, security and city services on the same pole
These four match the kits above. Open one to see which neighbouring product takes the order or the device.
Settle the pole and the billing boundary first
How do smart poles and charging operations split the work?
This page records which pole a charger hangs on, and shows online status plus a share overview. Orders, prices, payment and invoices are completed in charging operations.
How does this split from the IoT base?
Protocols, thing models and device access live in IoT device management. Smart poles consume online status, brightness and sensor readings, and run group policy, alarms and tickets.
Can the security page play video?
The security page counts whether cameras, help points and broadcast are online, and joins linkage. The video stream comes from the security platform or the IoT base.
Can the pole counts and amounts on this page be cited?
Do not cite them directly. Figures on the map, the dimming bar and the share cards explain the layout. External use takes the ledger, a confirmed EMC sheet, and orders in charging operations.
Can the roof PV supply the charger?
Roof PV is auxiliary power for low-voltage, communications and part of the lighting. The charger’s main supply is metered separately and posts apart from lighting savings.
Do EMC shares and charging income land on one line?
They post separately. EMC confirms savings as baseline energy minus measured energy. Charging, ads and site rent each have their own line on the sharing ledger.
Start by fixing the poles and groups on one road
Tell us whether this is roadside light-and-charge, an information screen, security linkage, or street-light EMC. We will walk through the ledger, dimming, alarms and sharing for that scope.