Turn scattered resources into one response event
Loads, storage, distributed generation and chargers register as flexible resources. MeetCarbon Cloud runs an event from invitation through bidding, execution, verification and settlement. On-site control systems stay with the owner.
See how devices connect- 1
- Resources to settlement
- 2
- Soft and hard commands
- Core
- Demand response
From resources to payout, on one chain
After an invitation arrives, assessment, bidding, execution, verification and settlement stay on the same record.
- 1
Onboard
Customers, sites and flexible resources enter the pool.
- 2
Invite and bid
Size the capacity, confirm with customers, then file the bid.
- 3
Monitor
Dispatch the plan and watch the curve against deviation.
- 4
Verify
Score the response and performance against a baseline.
- 5
Settle
Match the market statement and split aggregator and customer shares.
The main chain finishes the event. Rules and records sit beside it
Operations move event by event. Market rules, interface quality and the audit trail stay on the same files.
- 01
Resource center
Customers, sites and meters, plus loads, storage, generation and chargers, as flexible capacity.
- 02
Invitation and bid
Receive an invitation, check reachable capacity and conflicts, then validate and submit the bid.
- 03
Clearing and plan
Take the clearing result and split the target across customers, resources and strategies.
- 04
Execution watch
Send commands and keep the curve, deviation and alarms on the event.
- 05
Verification
Manage baselines, calculate the response and produce the performance pack.
- 06
Settlement
Reconcile the market statement and assessment, then split shares and issue statements.
Markets and rules
Configure products, assessment and bid checks. Demand response is the current main line.
Operations and trace
Interface status, data quality and key actions stay reviewable for the shift and for audit.
Soft commands first. Hard commands open resource by resource
Both can exist together. Today the usual path is to notify the customer or the on-site system. Automatic control turns on only after authorization and a passed control test.
Soft command
Default todayThe platform builds the plan, notifies the customer or on-site system, then collects the curve.
Fits the first demand-response events and a customer joining for the first time. The responsibility line stays clear.
Hard command
Per resourceOn a locked plan, the platform sends control to the on-site system or device and takes the result back.
Fits resources that are authorized, tested, and expected to respond faster.
Three checks before hard control
Two-person review
Dispatch, plan lock and batch control need a second confirmation.
Allowed hours
Commands go out only in the hours the customer authorized. Production blackout hours stay off.
One-step rollback
A command can be withdrawn, with the drill and the action kept on record.
Hard control also needs a signed authorization, a passed device test and acceptable meter quality. Until then the resource stays on soft commands.
Finish demand response first
Other products open with provincial rules and the required system connection. Status is marked separately.
Demand response
Main linePeak shaving and valley filling, on an hourly scale. Invitation through verification runs on this line.
Peak regulation
PartialHourly ancillary service, enabled per project once dispatch-side conditions are met.
Frequency regulation
LaterSeconds to minutes. It depends on dispatch access and hard control.
Reserve
LaterMinute-scale ancillary service, scheduled with dispatch access.
Spot
LaterEnergy trading, 15 minutes to an hour, after node and market rules are in place.
Forward
LaterMonthly and annual energy, assessed against the trading rules on their own.
One resource binds to a single virtual power plant. Bids check that it is not aggregated twice.
The aggregator runs the event. The customer confirms. Finance reconciles
A regional desk sees the roll-up. Each role stays inside its own customers, events and statements.
Aggregator ops
- Assess invitations and file bids
- Split plans and watch execution
- Review verification and shares
Customer
- Register resources and confirm strategy
- Accept or decline an invitation
- See execution and revenue
Regional desk
- See regional flexible capacity
- Review compliance
- Roll up statistics without editing operations
Finance and audit
- Match the market statement
- Open customer bills
- Read the action log
The platform orchestrates the event. On-site control stays in the customer system
The virtual power plant covers onboarding, orchestration, monitoring, verification and settlement. The items below stay where they are and connect in.
- IoT device management
Device access
Meters, chargers and gateways — presence, collection and control — go through IoT device management.
- Energy management
Energy ledger
Usage, analytics and reports are calculated in energy management. Event curves come from the meter points.
Customer EMS / BMS
On-site energy and storage control stay with the owner. This platform sends the plan or command and takes the result back.
Trading and dispatch
Invitations, clearing and dispatch orders come from provincial trading, load-management or dispatch systems. The platform receives, checks and returns them.
General ledger
Settlement figures can be pushed to corporate finance. Invoices and the ledger are not issued here.
Align these before joining an event
How do the virtual power plant and energy management split the work?
Energy management runs day-to-day usage, analytics and reports. The virtual power plant runs how flexible resources join an event: invitation, bid, execution, verification and shares. Both can use the same meter points.
Can we join demand response without automatic control?
Yes. A soft command notifies the customer or the on-site system, they confirm execution, and the platform monitors and verifies. Hard commands open per resource after authorization, a control test and a rollback drill.
Are frequency regulation and the spot market available now?
Demand response is the current main line. Peak regulation is partial, per project. Frequency regulation, reserve, spot and forward markets need dispatch or trading access, and are called out before they open.
Can one device serve two aggregators at once?
No. A resource binds to one virtual power plant. Bids check for a second aggregation.
How does revenue reach the customer?
The market statement and assessment are matched first, then split to the aggregator and the customer by the configured rules, with a reconciliation. Rule changes stay on record.
See whether the resources you have can join
Tell us the resource types, the province and how control works today. We will demo and say how far an event can go.