Platform

The control layer between charger behaviour and business outcomes.

Vampire.Energy observes what the infrastructure can do, decides what it should do, executes within physical limits, and preserves the evidence surrounding every charging outcome.

Platform layers

Every charging decision starts with what is actually happening.

The layers share one session context. Charger understanding informs control; control executes business and energy intent; every result feeds the next decision.

01

Understand

Charger Truth

Build a reliable view of the physical charger and the vehicle connected to it, informed by field and certification realities.

Model and capabilities Firmware and configuration Connectivity and state Vehicle compatibility Session telemetry
02

Act

Operational Control

Turn the shared session state into safe, traceable actions across chargers, connectors and sites.

Session control Charger configuration Remote operations Load constraints Policy execution
03

Connect

Business Workflows

Carry charging through the identity, commercial and operational systems that define whether the session delivered value.

Authentication Tariffs Billing Roaming PMS, fleet and enterprise integrations Business outcomes
04

Optimise

Energy Intelligence

Shape how and when charging happens around physical limits, energy conditions and external signals.

Site capacity Energy availability Cost Schedules Solar External and grid signals

Session flow

A session is a chain of decisions and handoffs.

Power delivery is only one part of the outcome. Identity, policy, energy, metering and business systems must stay aligned through settlement.

01
electric_car

Vehicle

Connects and requests energy

02
ev_charger

Charger

Reports state and capability

03
badge

Authentication

Validates who may charge

04
policy

Charging policy

Sets limits and intent

05
bolt

Energy delivery

Allocates available power

06
speed

Metering

Records delivered energy

07
receipt_long

Billing / roaming

Produces the commercial record

08
task_alt

Business outcome

Completes the surrounding workflow

A charger being online does not mean the charging outcome succeeded.

Session diagnostics

See where a session diverged from the expected outcome.

Vampire.Energy is designed to preserve available evidence across the session chain, so teams can isolate a divergence instead of treating every unsuccessful outcome as a charger fault.

Charger

Faults, configuration and connector state

ev_charger

Vehicle

Handshake, requested limits and compatibility

electric_car

Authentication

Credential, contract and roaming response

badge

Policy

Eligibility, tariff and power profile

policy

Energy

Capacity, schedule and site signals

bolt

Session execution

Start, stop and state transitions

sync_alt

Billing / roaming

Meter evidence, CDR and settlement

receipt_long

Business integration

PMS, fleet, ERP or customer-system result

account_tree

Session trace

Where expected and observed state diverge

txn_8821
11:04:02 Charger ready; connector available Matched
11:04:03 Vehicle connected; handshake complete Matched
11:04:04 Authentication provider did not respond within policy window Diverged
11:04:34 Charging policy not executed; energy delivery not started Not reached

Expected outcome

Authenticated session with an applied charging policy

Diagnostic result

Charger and vehicle healthy; divergence isolated to authentication

Energy control

The same charging session becomes an energy decision.

Once charger state and operational intent are understood, the platform can shape power delivery around the site, the schedule and changing energy conditions.

Illustrative site envelope

Capacity becomes an operating constraint

energy_savings_leaf

Site capacity

Fixed limit

Base demand

Observed

Charging envelope

Available

Active charging

Allocated

Operational reserve

Protected

Open architecture

Open by design, not tied to a proprietary hardware ecosystem.

Standards define the interfaces. Observable messaging, APIs and business-system integrations make those interfaces operational in the field.

OCPP

Communication, configuration and session control between chargers and the platform.

ISO 15118

Vehicle-to-charger communication, identity and Plug & Charge workflows.

OCPI

Roaming, token exchange, charge detail records and settlement workflows.

OpenADR

External energy and flexibility signals translated into charging policy.

Integration patterns

What is real today

Built depth, stated plainly.

The platform is grounded in protocol communication, charger and firmware understanding, distributed systems, business integrations and energy orchestration. Scale figures describe architectural intent; pilots describe validation activity; neither is presented as an installed-base claim.

Interfaces

OCPP + APIs

Observable infrastructure communication and system integration.

Context

Vehicle + site + business

Control decisions grounded in more than charger reachability.

Validation

Public engineering record

Open-source gateway work and publicly documented interoperability testing.

See evidence, standards and claim boundaries arrow_forward

One platform. Different operational outcomes.

See how the same technology supports energy providers, fleets, charging operators and hospitality.

Explore Solutions arrow_forward