Charge, SOC and revenue, on one operations desk
MeetCarbon Cloud energy storage operations covers commercial and behind-the-meter storage: multi-site control, charge and discharge strategy, safety alarms, demand-response and frequency-regulation events, plus energy and revenue reports. Device protocols land in IoT or a gateway. This product runs operations, dispatch and accounting.
- Multi-site
- One desk, compared sites
- 4 types
- Arbitrage, DR, regulation, capacity
- 4 levels
- Alarms from critical to info
- PCS / BMS
- Racks filed by device type
- Arbitrage62%
- DR18%
- Regulation12%
- Capacity8%
- Cabinet 2 · rack temperature spreadMajor
- PCS-03 · comms lost for 6 minMinor
From connection to the ledger, along the same site
Six steps match the menus in the product. Collection stays on the device side. Strategy, alarms and revenue stay here.
- 01
Connect
Create the site, attach PCS, BMS and battery racks, and pick drivers and points.
Sites · Drivers - 02
Monitor
Read topology, operating state, live points and online status.
Site control · Asset register - 03
Dispatch
Set a peak-valley or demand strategy, pass protection checks, then send it and keep the receipt.
Dispatch strategy - 04
Safety
Grade, confirm, suppress and score alarms in one loop.
Safety alerts - 05
Events
Record demand-response and frequency-regulation execution and settlement.
Event center - 06
Revenue
Publish charge and discharge, revenue by type, and the split.
Reports
What you open in storage operations
The list groups running, dispatch and safety, and revenue and intelligence. Pick a module to see its tabs and what it does.
Overview
RunningThe home view rolls up SOC, live power, today’s energy and the revenue mix across sites, and lists alarms waiting for confirmation.
- Multi-site metrics on one screen
- Revenue split into arbitrage, DR, regulation and capacity
- Higher-severity alarms surface first
Tab names follow the product menus. Figures on this page are samples, not a site’s operating results or revenue.
Sites, devices and alarms each have their own states
Site lifecycle, device online status and alarm severity are recorded separately. Control and high-risk actions stay on operating sites.
Site
Which stage the site is in.
- siteUnder constructionRecords and topology can be edited; strategy is not sent yet
- siteOperatingMonitoring, strategy and revenue are all on
- siteMaintenanceAlarms can be suppressed; control needs a separate grant
Device
Whether communications are still live.
- deviceOnlinePoints are refreshing
- deviceOfflineNo report past the threshold, and an alarm opens
Alarm
From critical to info, the response differs.
- levelCriticalConfirm first; protection can follow
- levelMajorHandle the same day
- levelMinorFold into inspection
- levelInfoRecord only
9 statesOffline thresholds and severity follow site configuration. This page only shows how the product separates states.
Each role opens a different door
The same site data: operations reads revenue, maintenance reads alarms, dispatch reads strategy receipts.
How are SOC, energy and revenue today, and which strategy needs approval?
- Multi-site overview
- Revenue by type
- Strategy approval
See the spread before deciding how much to charge
Move charge, planned discharge, valley price, peak price and round-trip efficiency. Counted discharge cannot exceed charge times efficiency.
Counted discharge = min(planned discharge, charge × efficiency). Efficiency is read as a combined round-trip figure.
- Counted discharge
- 1,760 kWh
- Discharge income
- 1,848
- Charge cost
- 700
- Spread
- 1,148
This calculator only sketches energy and price. It does not forecast tariffs and it is not investment advice. Actual revenue also includes demand charges, losses, service fees and the split.
From strategy to the ledger, in one record
The dispatcher sets the strategy, protection checks it, dispatch returns a receipt, and revenue lands in the report.
- 1Set the strategy
Write hours and power for peak-valley or demand.
- 2Pass protection
Check SOC bounds and power caps. Out-of-limit plans are not sent.
- 3Keep the receipt
The site returns success or the failure reason.
- 4Read execution
Compare the execution log with the planned curve.
- 5Book revenue
Energy and revenue by type go into reports. The split is a separate sheet.
Operations and the ledger live here. Collection and invitations live next door
Storage operations covers how a site runs, how strategy is sent, how alarms close and how revenue is recorded. Protocols, work orders, invitations and bids each have a product.
This product owns
- Multi-site control, topology and device monitoring
- Charge and discharge strategy, protection limits and execution receipts
- Alarm grading, suppression and risk scores
- Execution and settlement records for demand response and frequency regulation
- Energy reports, revenue by type and the split sheet
- Battery health, strategy suggestions, revenue forecasts and draft operations reports
Neighboring products own
- IoT device managementOpenThing models and TCP, MQTT and Modbus parsing and collection.
- Smart operationsOpenCross-asset equipment files, inspection and work orders. Storage alarms close in this product.
- Virtual power plantOpenInvitations, bids, clearing and aggregated dispatch. Storage records this site’s execution.
- Power-trading assistantOpenMarket data, offers and backtests. Storage does not file the bid.
- Solar operationsOpenPV fleet monitoring and generation revenue. A PV-storage site can be viewed side by side.
Grid dispatch signals come from the grid or the virtual power plant. After the split sheet is produced, the bank transfer happens in finance.
Five steps to run the first site
A site and its devices come first, then topology and strategy, then reports.
- 1Site name, address, rated power and capacity
- 2Vendor and model for PCS, BMS and racks
- 3Gate meter and tariff periods
- 4Protection requirements such as SOC bounds and power caps
- 5Revenue split ratios, if an owner or investor is involved
Historical energy can be backfilled into reports. A backfill does not replace the meter or the settlement statement.
- 1Create the site
Enter the site and mark it under construction or operating.
This step produces · Site record - 2Attach devices and drivers
File PCS, BMS and racks, then pick a driver and point map.
This step produces · Device list - 3Draw the topology
Connect the gate meter, PCS, racks and gateway.
This step produces · Topology - 4Set strategy and protection
Write a peak-valley or demand strategy and apply a protection template.
This step produces · A strategy that can be sent - 5Publish reports
Once operating data exists, export energy and revenue.
This step produces · Report files
Many sites, an audit trail, and export
Storage operations runs on MeetCarbon Cloud and shares organization and permissions with solar and the virtual power plant.
One account watches many storage sites and compares them.
Operator, owner and investor each get a line by ratio.
Strategy dispatch, control, alarm confirmation and export record who did it and when.
Energy, revenue and the split sheet can be exported for reconciliation.
Annual subscription. Published prices are on the pricing page and follow the contract.
Can be deployed in the customer environment. Implementation is listed separately on the pricing page.
Who opens this desk first
Teams that already run behind-the-meter storage, or that want storage in the power bill and the demand charge.
Where strategy, alarms and revenue stop
These are the lines customers check most often.
Who sends the strategy?
The dispatcher sets hours and power under dispatch strategy, then sends it after the protection check. AI strategy suggestions stay as suggestions and are not sent automatically. Every send has a receipt.
Does closing an alarm mean the work order is done?
Confirm, recover and close happen in storage safety alerts. Inspection work orders that span solar, charging and buildings live in smart operations. The two can be compared. Neither replaces the other.
Does the split sheet pay out automatically?
The split module builds a sheet for the operator, owner and investor by ratio. The bank transfer happens in finance. Storage operations does not start a payment.
Does an AI forecast guarantee revenue?
Battery health, strategy suggestions and revenue forecasts are labeled as forecasts or suggestions. The peak-valley sketch on this page only illustrates quantities. Actual revenue follows the meter, the tariff and the settlement statement.
How is this split from the virtual power plant?
The virtual power plant aggregates resources and handles invitations, bids and clearing. Storage operations records whether this site executed the event and writes the settlement into revenue. Grid instructions are not invented here.
Lay out strategy and revenue for one site first
Tell us rated power, tariff periods and who sends strategy today. We will walk through control, dispatch and reports in this structure.