Cold storage
Compressor staging inside temperature and defrost boundaries
Thermal guard active
Loadlume Dispatch
Move flexible demand without losing control of the operation.
Turn an approved opportunity into asset-level instructions, monitor delivery in real time, handle exceptions, and preserve the complete event record.
Event EV-240716Global portfolio · live response
ActiveTarget response4.8 MWDelivered now4.73 MWEvent window14:00–16:00
The dispatch problem
A portfolio target is not yet an operating plan.
A credible event must decide which assets participate, what each one should do, who needs to approve it, how instructions are delivered, and what happens when reality moves away from the plan.
Loadlume Dispatch keeps those decisions connected from the first allocation to the final measured response.
PlanAssets, targets, timing, recoveryApproveWarnings, holds, operator authorityDeliverInstructions and acknowledgementsMonitorResponse, constraints, exceptions
The live event sequence
One event record from approval to evidence.
Follow Event EV-240716 as the portfolio moves from a forecast opportunity into a measured operational response.
Event EV-240716Global portfolio · 14:00–16:00 UTC
Draft planPortfolio target4.8 MWParticipating assets8 / 8DeliveryPending
Asset13:4514:0015:0016:00
Cold Storage 011.4 MW EV Depot1.2 MW Battery BESS-21.6 MW Plant A0.6 MWControl policy
Choose how authority moves through the event.
Automation should match the operating agreement. Pre-approved assets can respond automatically, while sensitive sites can retain explicit human hold points.
Event EV-240716Automatic control policy
Policy activeEvent plan4.8 MW targetPolicy checkPre-approvedInstruction8 / 8 assetsResponse98.6%
Asset execution
Translate one target into instructions each asset can follow.
The portfolio plan stays consistent while every asset receives a command shaped by its control path, limits, and recovery requirements.
AssetInstructionTargetDeliveryState
Cold Storage 01Endpoint 01Reduce compressor load1.4 MW14:00–16:00Acknowledged
EV DepotEndpoint 02Pause flexible charging1.2 MW14:00–16:00Delivered
Battery BESS-2Endpoint 03Discharge to site1.6 MW14:00–16:00Delivered
Plant AEndpoint 04Shift auxiliary process0.6 MW14:00–16:00Monitoring
Event EV-240716Live delivery · 15:18 UTC4.73 / 4.80 MW
Live operations
See the response while there is still time to act.
Dispatch keeps the planned response, measured delivery, acknowledgements, constraints, and remaining event target visible on the same operational clock.
Delivery98.6%Assets responding8 / 8Open exceptions1
Exception handling
Protect the event without hiding the deviation.
When an asset misses an instruction, Loadlume keeps the reason visible and shows the effect of each response option before the portfolio is changed.
EV Depot · delivery below planReview required
15:12:08Measured response fell 0.18 MW below targetCharger group C returned to service early
Option 01Rebalance to Battery BESS-2+0.18 MW · state of charge remains above 34%Recommended
Option 02Accept portfolio shortfallRevised delivery estimate 96.4%
Dispatch by asset
Different instructions. One coordinated response.
The dispatch language changes with the equipment while acknowledgement, monitoring, exception, and evidence states remain consistent.
EV fleets
Charging pauses that preserve departure readiness
Departure check activeBattery systems
Power instructions with state-of-charge and reserve limits
SoC guard activeIndustrial sites
Process shifts aligned with production hold points
Operator hold activeVerification handoff
Every event leaves a complete operational trail.
Approvals, instructions, acknowledgements, measurements, exceptions, and final delivery remain together for review and settlement.
Event EV-240716Evidence building
Plan approved13:48:11 · Marta Kowalska · 4.8 MW
Instructions acknowledged13:58:42 · 8 of 8 assets
Response measured14:00–16:00 · 5-minute intervals
Exception resolved15:13:04 · 0.18 MW rebalanced
Verified delivery98.6%Evidence ready for review
Dispatch FAQ
Questions before coordinating a live response.
Control boundaries, approvals, telemetry, and exception policy are defined during the initial dispatch assessment.
Does Loadlume control equipment directly?
Dispatch can coordinate instructions through the control path agreed for each asset. That may be an automated endpoint, an existing control system, or an operator-led workflow. The product keeps the chosen control boundary visible.
Can operators stop or change an event?
Yes. Operator authority, hold points, overrides, and abort conditions are part of the event plan. Changes are recorded with their effect on the remaining portfolio target.
How are failed acknowledgements handled?
An unacknowledged instruction is surfaced immediately. The event can pause, remove the asset, or rebalance the remaining target according to the configured operating policy.
What is monitored during delivery?
Loadlume compares the planned response with live measurements while continuing to watch asset constraints, data quality, site status, and the recovery conditions that follow the event.
How does Dispatch connect to verification?
The final event record combines the approved plan, instructions, acknowledgements, interval measurements, exceptions, and calculated delivery so the performance claim can be reviewed and exported.
Start with one event
Turn a credible forecast into a controlled response.
Bring one portfolio, its control paths, and the operating rules that matter. We will help define a practical first dispatch scope.