Connected cold storage, EV fleet, battery system, and industrial assets

Loadlume Assets

Build a live operating model of every flexible asset.

Bring sites, meters, equipment, schedules, and constraints into one structure that shows what is connected, what is available, and what still needs attention.

Global portfolioAsset operating model
Live
Connected assets12Available now8.3 MWNeeds review2
Global portfolio Site 01 6 assets Cold Storage 01 1.6 MW EV Depot 2.4 MW BESS-2 3.1 MW
Cold Storage 01Refrigeration system
Available
Temperature−20.4°COperating limit−18°C to −22°C
Available capacity1.6 MW
14:0016:00
4 constraints passedUpdated 13:47 UTC

The operating problem

A meter tells you what happened. It does not tell you what can move.

Flexible demand depends on relationships that interval data alone cannot explain. A compressor belongs to a refrigeration system. That system belongs to a site. Its availability depends on temperature, schedule, operator rules, and what happened moments ago.

Loadlume Assets is designed to keep those relationships intact, so an availability number can be understood before it is used.

HierarchyPortfolio → site → meter → equipmentLive stateTelemetry, status, and recent behaviorSchedulesProduction, departure, and operating windowsConstraintsLimits, approvals, and operator-owned rules

The live asset model

One asset. Four layers of operational truth.

Follow Cold Storage 01 as the same operating model gains the context required for a credible flexibility decision.

Global portfolio12 connected assets · Last model refresh 13:47 UTC
Live model
Structure

Map the operating hierarchy

Operating model
Available now8.3 MWConstraint changes2 pendingData qualityHealthy
AssetTypeCapacityState
Cold Storage 01Refrigeration1.6 MWAvailable
EV DepotCharging2.4 MWAvailable
Battery BESS-2Storage3.1 MWAvailable
Plant AIndustrial process1.2 MWConstrained

From inventory to availability

Build the model without separating it from the operation.

Each step adds context to the same asset record. The result is not a static catalogue; it is a living foundation for forecasting, dispatch, and evidence.

Plan an asset assessment
Cold storage loading operations
Cold Storage 01Live operating context−20.4°C
01

Connect the structure

Identify sites, meters, equipment, and the data sources that describe them.

12 assets mapped
02

Model the boundaries

Attach schedules, operating bands, site caps, and human approval rules.

6 active constraints
03

Calculate availability

Evaluate flexible capacity only where state, limits, and data quality support it.

1.6 MW available

Inputs and outputs

Fit the asset model around the systems already in use.

Start with practical data, preserve its source and freshness, and carry the operating context forward to the rest of Loadlume.

Operating inputs

Meter and telemetry dataContinuous or intervalSCADA / BMS contextState and control pointsOperating schedulesPlanned windows and deadlinesOperator constraintsRules and approvals
Loadlume AssetsShared operating model

Product outputs

Availability intervalsCapacity with boundariesConstraint changesVisible before decisionsForecast contextInputs for future windowsDispatch eligibilityAsset-level readiness

Built around real assets

Different equipment. Different limits. One operating language.

The model stays consistent without pretending that every asset behaves the same way.

01

Cold storage

Temperature bands, compressor cycles, defrost schedules

02

EV fleets

Departure deadlines, charger limits, required state of charge

03

Battery systems

State of charge, power limits, availability commitments

04

Industrial sites

Production windows, process limits, site demand caps

Traceable by design

Keep the reason behind every availability change.

A trustworthy asset model should show more than the latest value. It should preserve what changed, which source changed it, and how the decision state was affected.

Cold Storage 01 · Model historyLive
Temperature signal refreshedBMS-04 · −20.4°C · healthy
Defrost schedule updatedNext cycle moved to 15:40
Constraint check completedTemperature and site demand limits passed
Availability recalculated1.6 MW · 14:00–16:00 · forecast-ready

Assets FAQ

Questions before modeling a portfolio.

Technical scope and data availability are confirmed during the initial assessment.

How is an asset model created?

The first model combines available meter data, asset information, schedules, and known operating limits. Additional telemetry and control-system signals can be connected as the assessment develops.

Does every asset need live telemetry?

No. The model can begin with the data already available and keep the source quality visible. Live telemetry adds depth, but the platform should never imply a level of confidence the source data cannot support.

Can operating teams change constraints?

Yes. The intended workflow keeps operator-owned limits visible and traceable, including who changed a rule, when it changed, and which availability calculations were affected.

How does Assets connect to Forecast and Dispatch?

Assets provides the shared hierarchy, state, and constraint context. Forecast uses that model to estimate future availability, while Dispatch uses it to prepare and monitor an approved asset-level plan.

Can one portfolio contain different asset types?

Yes. Mixed portfolios are a core use case. Each asset keeps its own constraints while using a consistent operating structure for availability, decisions, and evidence.

Start with one portfolio

Turn your asset inventory into an operating model.

Bring the data, schedules, and limits you have today. We will help identify the right first modeling scope.

Discuss your assets Talk to Loadlume