Parking and charging points, on one network
MeetCarbon Cloud parking and charging network management puts lots and charging sites on one point network. The operations map shows where they sit. WPCI shows the index. The executive cockpit and command mode show the situation. The display wall is for playback. Lot orders and monthly passes stay in smart parking. Charging orders, chargers, and invoices stay in charging operations.
- One map
- Parking, charging, and combined sites
- WPCI
- An unaligned index is not shown as zero
- Cockpit
- Situation, duty, and follow-up
- Display wall
- Five groups, from overview to analysis
- Parking54%
- Charging32%
- Combined14%
- Riverside lot record incompleteIncomplete
- This month’s index basis is unalignedUnaligned
From points to the display wall
Points come first. The map shows where they sit. The index, cockpit, and command mode read the same network. The wall plays it back.
- 01
Register POIs
Attach lots, charging sites, and combined sites to the network. Incomplete records stay marked incomplete.
POI - 02
Open the map
See coverage, online status, and items still to check, by area.
Operations map - 03
Produce WPCI
The index follows the configured basis. If the basis is unaligned, the page says so and does not fill zero.
WPCI - 04
Read the situation
The cockpit summarizes points and the index. Command mode takes duty follow-up.
Cockpit · command - 05
Play the wall
The wall switches across overview, parking-and-charging situation, energy and safety, service, and analysis.
Display wall - 06
Network settings
Scope, layers, and playback settings sit in network configuration, and changes stay on record.
Settings
Walk the network menu
Seven items: operations map, POI, WPCI, executive cockpit, command mode, display wall, and network settings.
Operations map
See the networkSee where parking, charging, and combined sites sit, which points are attached, and which records are still incomplete.
- Switch by area instead of merging cities into one dot
- Online and incomplete stay apart
- A point opens its POI record
Point counts and index figures on the sample cards explain the layout. They are not a published index result.
Points, the index, and duty each keep their own mark
Incomplete means the record is short. An unaligned index is not shown as zero. Duty that is off is not shown as an open shift.
POI attachment
Whether the record can appear on the map.
- Coordinates, type, and source are presentAttachedAttached
- Coordinates, type, or source is missingIncompleteIncomplete
WPCI
A score appears only after the basis is aligned.
- Basis version matches the data sourceAlignedAligned
- Missing data is not shown as zeroUnalignedUnaligned
Command duty
Whether command mode is on duty.
- Follow-up can be logged to the shiftOn dutyOn duty
- An empty shift is not shown as activeOffOff
6 statesIndex parts and weights are kept in network settings. A published index follows the result issued by the compiling body or the authority.
Admin, index, duty, narration, and city coordination each open a different page
One point network. Someone completes records, someone reads the index, someone is on duty, someone plays the wall.
Which lots and charging sites does this network cover, and which records are still short?
- Online and incomplete on the map
- POI type and source
- Coverage in network settings
See the map, check points, read the index, then play it
A check starts on the map and ends on the wall. Each step can return to the POI and to network settings.
- 1Open the map
Online points and incomplete records decide whether to drill in.
- 2Check the POI
Open the record and fill coordinates, type, or source.
- 3Read the index
Confirm the basis is aligned before reading the score.
- 4Open the cockpit
Scale and the index become the situation view.
- 5Log follow-up
When duty is on, items to check stay on the record.
- 6Play the wall
Switch groups: overview, situation, or analysis.
The point network stays here
Aggregation, the index, the cockpit, command, the wall, and network settings stay in parking and charging network management. Lot orders and charging transactions have their own products.
This product
- Coverage and online status on the operations map
- POI records for parking, charging, and combined sites
- WPCI display, labeled unaligned when the basis does not match
- Executive cockpit and command mode
- Five display-wall groups
- Network scope, index basis, and playback settings
Neighboring products
- Smart parkingViewLot orders, fee rules, monthly passes, and gates. A lot can be attached to this network.
- Charging operationsViewCharging orders, chargers, tariffs, and invoices. A site can be attached to this network.
- Carbon benefitViewGreen-behavior points for people or merchants. An index part may cite them. Scoring stays off the points ledger.
Official index publication and assessment scores stay with the compiling body or the authority. This product keeps the basis version and the index already shown. Parking charges and charging payments are not started from this page.
Five steps to connect one network
Set the scope and the points, write the index basis, open the map, then connect the wall.
- 1City or project scope
- 2Lot and charging-site list with coordinates
- 3Index basis and version
- 4Wall groups to play
Until points are attached, status stays incomplete and missing data is not written as zero. Until the index basis is aligned, the score is not shown as zero.
- 1Set the scope
Write the city or project this network covers.
Done when · Scope opens - 2Attach POIs
Add lots, charging sites, and combined sites.
Done when · Points have coordinates - 3Set the index basis
Write the basis version so aligned and unaligned stay distinct.
Done when · The index page can show status - 4Open the map
Confirm online and incomplete points are both visible.
Done when · Map opens - 5Connect the wall
Play by group, with the same figures as the back office.
Done when · The wall switches
Many projects, a trail, export
Each city or project keeps its own network. Basis changes, duty follow-up, and playback settings stay on record. Deployment and price are on the pricing page.
Each network has its own scope and points. Cities are not merged into one number.
Basis and version sit in settings. Unaligned stays labeled.
Command follow-up, basis edits, and playback changes are kept.
The point list and the index summary export on a cycle.
Opened per project, on the same MeetCarbon Cloud account as parking and charging.
When point data must stay on the internal network, the platform can run on the customer side.
A city, a park, a briefing, and a duty shift can sit on this network
Point records hold public parking and charging sites together. A published index still follows the result issued by the compiling body.
The point network, the parking ledger, and the charging ledger
Five checks before go-live.
How does this divide work with smart parking?
Smart parking covers lot orders, fee rules, monthly passes, and gates. Parking and charging network management attaches a lot as a point. Fees and monthly passes are not edited here.
How does this divide work with charging operations?
Charging operations covers orders, chargers, tariffs, and invoices. A charging site can be a POI on this network. Start, stop, payment, and invoices stay in charging operations.
Is WPCI an assessment score?
The index on the page follows the configured basis and is marked as a sample or as unaligned. Assessment scores and public release follow the compiling body or the authority.
Where do the wall figures come from?
The wall cites the same point network, the same index, and summaries already held by parking and charging. An unaligned index stays labeled on the wall and is not filled in as zero.
How does this divide work with carbon benefit?
Green-behavior points for people or merchants stay in carbon benefit. An index part here may cite green travel or energy saved. The two sides do not score each other.
Lay out parking and charging points for one area first
Tell us the city or park, whether the points already have coordinates, and whether you need an index and a wall. We will walk through the map, the index, and playback for that scope.