Assets & site systems
- Electricity generated and used, remaining battery charge, charging status, and equipment limits.
KUNIES is designed to connect a business’s solar, battery, electricity-use, and market data. See costs and revenue together, compare trading strategies with AI, automate alerts and reports, and track whether instructions were carried out and results matched expectations.
Connect data →︎ Compare opportunities →︎ Track execution →︎ Understand changes.
Equipment records generation, markets provide prices, and trading systems record outcomes. KUNIES is designed to connect these records by site and time so teams can compare what they expected with what actually happened, without manually combining separate reports.
KUNIES is building an independent energy connectivity and automation platform. It connects existing systems, bringing equipment data, market information, team workflows, and change tracking together so cost analysis and trading operations share the same data.
Track API, data, and rule changes; identify affected calculations and workflows.
Connect conditions, approvals, notifications, and returned results in traceable workflows.
Map prices, tariffs, contracts, and settlements with effective versions.
Align assets, measurements, and sites across vendors, retaining source and quality.
↑︎ Sources support applications above. ↻ Change tracking spans the other three layers; results return to connected systems.
Formats differ, rules vary, workflows run separately, and sources keep changing. When each application handles these independently, integration, workflow development, and maintenance are repeatedly rebuilt.
Four layers address all four breaks.Start with commercial and industrial energy service providers and solar and battery operators. What energy is available to trade? Is now a suitable time? Did equipment carry out the instruction? Did revenue match expectations? Which steps need updating when data or rules change?
Deliver a complete process, then expand sites and applications.AI assists participation, capacity, and delivery-risk assessments with evidence and uncertainty, alongside field mapping and change interpretation. Transactions and control instructions remain subject to authorization, review, and safety constraints.
Consider a business trading electricity from solar panels and batteries: check available energy, compare strategies, track results, and identify what changes when systems or rules are updated.
“Message sent” does not mean “trade accepted,” and “instruction received” does not mean “electricity delivered.” Check each step separately to see where a trade is blocked and whether actual revenue matches expectations.
● Solar generation ● Consumption
| Source | Site | Interval | Quality |
|---|---|---|---|
| PV monitoring | Site A | 15 min | Healthy |
| Battery EMS | Site A | 15 min | Data gap |
| Utility meter | Site B | 15 min | Healthy |
Battery EMS has 2 gaps. Check completeness before using related analysis.
Compare participation windows, capacity, and risk under different price, generation, and storage assumptions. Preserve source versions; simulated results are not guaranteed returns.
| Checkpoint | Evidence / reference | Status |
|---|---|---|
| Market A / Product 01 | Price, interval, eligibility | Source version retained |
| Market B / Product 02 | Price, currency, settlement rules | Eligibility to review |
| Market & aggregator requirements | Product conditions v03 | Response deadline to verify |
| AI strategy simulation | Baseline / lower generation / higher price | Compare revenue and delivery risk |
Authorized reviewer: energy trading owner. An AI recommendation does not submit a transaction.
Track command receipts separately from telemetry. Do not mark delivery complete without measured evidence.
| Checkpoint | Evidence / reference | Status |
|---|---|---|
| Submission response | EVT-024 / SUB-01 | Accepted |
| Award / assignment | EVT-024 / AWD-01 | Assigned |
| Device instruction | EVT-024 / CMD-01 | Acknowledged |
| Measured delivery | EVT-024 / METER-01 | Telemetry delayed · Review |
| Delivery & settlement | EVT-024 | Pending reconciliation |
Exception handling: notify the site owner, reconcile communications and telemetry, and avoid blind resubmission.
| Source | Change | Impact | Review |
|---|---|---|---|
| Battery API | power / kW →︎ W | High | Review |
| Aggregator API | Acknowledgement states changed | Medium | Assigned |
| Market rules | Settlement interval version updated | Low | Checked |
The power-unit change may affect 2 workflows. Revalidate after correction.
Cost analysis, asset performance, notifications, and transaction-result analysis are applications built on the four-layer foundation. Conclusions should trace back to data, applicable rules, and execution outcomes.
Compare available energy, market prices, and trading requirements to simulate potential revenue and risks across strategies.
Combine applicable tariffs, contracts, and settlement results to explain expected-versus-actual differences.
Track submissions, awards, acknowledgements, and delivery separately; route rejections, timeouts, and telemetry gaps to owners.
Help finance understand the cost and operations know what to check. Organize the evidence around three simple questions.
Shape your first report with us ↗︎Separate energy, demand, and other charges, with the billing period and source bill attached.
Compare usage, peaks, rates, and billing days. Separate verified drivers from hypotheses.
Route review items to their owners, with notifications and reports that fit your process.
Change Intelligence is being designed to connect a change to its operational impact, preserving evidence, versions, and review items.
Planned coverage depends on accessible, authorized sources. Detecting a change does not by itself establish its legal interpretation or compliance status.
Our initial focus is commercial and industrial energy operations. If your business depends on work across systems, vendors, or sites, we want to start with one real process and a verifiable scope.
Start with one market product, one site, and one authorized workflow.
Discuss your use case ↗︎Start with a cost discrepancy and the sources behind one site.
Discuss your use case ↗︎Start with two sources and one operational exception.
Discuss your use case ↗︎Start with API documentation, access permissions, and a shared customer need.
Discuss your use case ↗︎You have a named data owner, sources that can be accessed with authorization, and a recurring integration or operational problem. Together we confirm data availability, deliverables, and acceptance criteria before expanding.
Start with one clear problem: scattered data, unexplained bills, unclear trade status, or reports rebuilt by hand. Together, we define the systems to connect, the first workflow, and how to measure the result.
Our initial focus is energy service providers for commercial and industrial businesses, multi-site businesses, solar and storage operators, and equipment or software partners with authorized data access and a clear integration or operational problem.
The product is designed to work with existing systems. Source availability, data frequency, and access permissions must be confirmed for each project.
This page presents our product direction and interactive concepts, not a list of live capabilities. We are seeking pilot collaborators to define data access and a deliverable scope.
AI is intended to assist assessment, evidence preparation, and risk explanation. Submissions or control commands depend on customer authorization, approvals, equipment safety constraints, and market/aggregator integration requirements. Scope must be validated with each partner.