Put flexible loads on one ledger first
Air conditioning, production lines, cold chain, charging and lighting each have a limit on how far they can move, how long they can hold, and which hours stay off limits. MeetCarbon Cloud splits a call across those loads and files an execution receipt against the curve. Invitations, clearing and settlement stay on the virtual power plant.
See invitations and settlement- 5
- Load types
- 1
- Execution chain
- Filed
- Execution receipt
Five load types, each with its own way to move
The ledger records how a load can move and which constraints stay off limits. One site can hold several types.
- Adjustable
Air conditioning
How it movesRaise the setpoint inside the comfort band, or ease chiller output for a short time.
Typical limitKeep temperature and humidity floors while people are in the space. Do not stop fresh air.
- Shiftable
Production line
How it movesMove a flexible process outside the call window.
Typical limitDelivery dates and takt time come first. Blackout shifts stay out of the split.
- Adjustable
Cold chain
How it movesUse stored cooling and lower compressor load briefly.
Typical limitRoom temperature stays inside the product limit. Recovery time is written on the ledger.
- Shiftable
Charging
How it movesShift or reduce power inside the allowed charging window.
Typical limitDeparture time and minimum state of charge come first. A floor for public chargers is agreed separately.
- Interruptible
Lighting
How it movesDim by zone, or switch off areas that are not in use.
Typical limitWork-plane illuminance stays at the site requirement. Emergency lighting does not participate.
Three ways to move, with the limits written on the capability
Assessment records notice time, how long it can hold, ramp and the red line. A call is split only across capabilities already written down.
Interruptible
- Notice
- Can be short, if the site can actually stop.
- Hold time
- Limited to the allowed outage.
- Ramp
- Time to restore supply or restart is recorded on its own.
- Red line
- Safety interlocks, emergency lighting and continuous processes stay out by default.
Shiftable
- Notice
- Long enough to cover preparation and a shift change.
- Hold time
- Usually one process or one shift.
- Ramp
- Follows the line or the charging queue.
- Red line
- Delivery dates, departure times and floor power cannot be moved.
Adjustable
- Notice
- Follows the equipment’s own response time.
- Hold time
- Bounded by comfort, room temperature or the process window.
- Ramp
- Steps up and down. Avoid a single full pull.
- Red line
- Comfort, product temperature and process settings come first.
From the ledger to the receipt, on the same record
After a call arrives, the split, the trace and the receipt stay on that record, so you can check later whether the load moved.
- 01
Load ledger
Customers, sites and flexible loads enter the pool, constraints included.
- 02
Call received
Take a dispatch order or a plan already locked by the virtual power plant, and check the window and the target.
- 03
Split to loads
Break the target across loads that sit outside their red lines.
- 04
Curve watch
Compare actual load with the target band. Deviation stays on this record.
- 05
Execution receipt
File the window, the target and the curve for the response desk and the customer.
The main chain finishes one call. The side rails keep the red lines and the handoff
Operations move call by call. Constraints, virtual-power-plant plans and dispatch returns stay on the same files.
Load ledger
Customers, sites and meters, plus air conditioning, lines, cold chain, charging and lighting, as flexible loads.
Flexibility assessment
Mark each load interruptible, shiftable or adjustable, with notice, hold time, ramp and a red line.
Call split
After a target arrives, use only loads outside their red lines and assign the reduction or the shift.
Curve watch
Inside the window, compare actual load with the target band. Deviation and alarms stay on this record.
Execution receipt
File the window, the target, the curve and who confirmed, as a receipt you can reopen.
Constraints and red lines
Comfort bands, takt time, room temperature, charging windows and illuminance are conditions that stay out of the split.
Virtual power plant and dispatch
A plan can come from the virtual power plant. An order can come from dispatch or load management. This product splits, watches and returns the result.
The service firm builds the ledger. The desk runs the call. The site holds the red line
Dispatch sees the return. Each role stays inside its own sites and calls.
Energy service firm
Ledger and assessment- Register loads and meters
- Assess flexibility and red lines
- Keep the on-site confirmation path
Demand-response desk
Call to receipt- Receive a call and split it
- Watch the curve and the deviation
- File the execution receipt
Power user
Its own loads- Confirm the flexible window
- Mark production red lines
- See whether this call moved
Dispatch liaison
Orders and returns- Receive dispatch or load-management orders
- Return the execution result
- Leave the dispatch plan unchanged here
This page keeps the load ledger and the receipt. The market event stays on the virtual power plant
Load aggregation covers registration, splitting, watching and the receipt. The items below stay where they are and connect in.
- IoT device management
Device access
Presence, collection and control for meters, gateways and controllable devices go through IoT device management.
- Energy management
Load curves
End-use electricity, statistics and reports are calculated in energy management. Curves for a call come from the meter points.
- Virtual power plant
Invitations and settlement
Invitations, bids, clearing, verification and settlement run on the virtual power plant. This product supplies load capability and the execution receipt.
Grid dispatch
Call orders come from dispatch or load management. This product receives, splits, watches and returns them. It does not issue orders to the grid.
Power trading
Spot and forward trading stay with the exchange and the trading desk. Load aggregation does not file a trading bid.
Align these before the ledger is built
How do load aggregation and the virtual power plant split the work?
Load aggregation registers flexible loads, splits a call and files the execution receipt. The virtual power plant runs invitation, bidding, clearing, verification and settlement. Both can use the same load curves.
Can we build the ledger before automatic control is in place?
Yes. The ledger records capacity, hold time and red lines first. When a call arrives, the site confirms execution, and the curve becomes the receipt. Automatic control opens per load after authorization and a passed test.
Can a production line with a delivery date join?
Register it as shiftable. Move the load only inside windows the takt time and the delivery date allow. Red-line hours stay out of the split.
Where does a call come from?
From grid dispatch or a load-management system, or from a plan already locked on the virtual power plant. This product receives, splits, watches and returns the result.
Who receives the receipt?
It stays on the call record for the response desk and the power user. When the event reaches market settlement, the virtual power plant cites this receipt for verification and the share-out.
See whether the loads you have can enter the ledger
Tell us the load types, the province and how control works today. We will demo and say how far the ledger can go.