Operate around successful sessions, not charger uptime.
A charger can be online while authentication, energy delivery, billing, roaming or the customer experience still fails. Vampire.Energy is designed to give operators visibility and control across the full session, from charger behaviour to business outcome.
Session outcome
Reachability is an input, not the outcome
Infrastructure signal
Charger online
Reachability confirmed
Operational question
Session succeeded?
Needs outcome context
What operations needs to know
Did the charging outcome succeed, and if not, where should the team act?
Operational control
Bring session context into the control loop.
From evidence to action
Join charger, driver, energy and commercial context so operators can decide, intervene remotely and verify the resulting state from the same operating view.
Session success
Online is a condition. Successful charging is an outcome.
Uptime tells an operator whether infrastructure is reachable. Charge success asks whether the complete driver, energy and commercial workflow worked as expected.
Uptime
Charger reachable.
A useful infrastructure signal, but not evidence that the charging outcome succeeded.
One operating condition
Driver authenticated
The expected credential and authorisation path worked.
Charging started
Vehicle, charger and policy reached an active session.
Energy delivered
Power flowed within site and session constraints.
Session completed
Start, stop and final state matched the expected flow.
Metering recorded
Delivered energy produced a usable session record.
Billing and roaming completed
The commercial workflow reached its intended outcome.
Session evidence
Know what actually happened.
Vampire.Energy is designed to correlate the dimensions that matter to operations instead of treating each subsystem independently. The intended result is clearer evidence of where the expected charging outcome diverged and where action belongs.
Charger
State and capability
Vehicle
Connection and response
Authentication
Authorisation result
Energy
Delivery and constraints
Metering
Recorded evidence
Commercial completion
Billing and roaming outcome
Operator consequence: one correlated record for explainable triage and action.
See the full session architecture arrow_forwardRemote operations
Turn visibility into operational control.
Diagnostics should lead directly to action. Shared session context helps operators decide what can be resolved remotely, what needs automation and what requires on-site intervention.
Observe the state. Apply policy. Act. Verify the result.
Observe
Correlate charger and session state.
Decide
Evaluate policy and available paths.
Act
Execute a remote or automated action.
Verify
Confirm the new state and outcome.
Session control
Remote start, stop and supported recovery paths.
Charger configuration
Apply traceable settings across compatible infrastructure.
Operational policies
Translate operating intent into consistent execution.
Capability awareness
Act with model, state, firmware and configuration context.
Workflow automation
Handle repeatable operating conditions consistently.
Resolution paths
Separate remote actions from field-service exceptions.
Site energy control
Operate chargers and energy together.
Operators need to make practical allocation decisions across sites and active sessions. The platform mechanics sit underneath; the operating priorities stay clear.
Stay within capacity
Respect site and connection limits.
Prioritise where needed
Allocate charging around operational need.
Use relevant signals
Apply tariff, solar or energy inputs where useful.
Billing & Roaming
Charging is incomplete if the business workflow fails.
A technically successful session still needs accurate metering, pricing, charge detail records, billing and roaming. Vampire.Energy is designed to keep those steps connected to the same operational context.
Metering
Record delivered energy.
Session record
Produce usable charge detail data.
Tariff
Apply the intended pricing logic.
Billing / roaming
Exchange records with relevant systems.
Business outcome
Complete the surrounding workflow.
One outcome, not separate modules: authentication, tariffs, billing, roaming, APIs and business integrations all participate in whether a session delivered operational and commercial value.
Mixed-estate operations
Scale infrastructure without scaling operational complexity at the same rate.
Consistent workflows depend on understanding what each charger can do. Model, capability, firmware and configuration context help operators automate the routine and focus attention on exceptions.
Consistent workflows across supported mixed estates.
Automation for repeatable operating conditions.
Exception-focused operational queues.
Central context without hiding hardware differences.
AC charger
Model and connector context
DC charger
Power and capability context
Site controller
Capacity and policy context
New hardware
Validated integration context
Mixed-estate context
Common workflows informed by actual charger capability.
Charger context
Reliable operations require understanding the infrastructure underneath the dashboard.
Charger behaviour, interoperability and correlated session context give operators better evidence for diagnosis and a clearer basis for safe control across supported infrastructure.
See the platform architecture arrow_forwardRun the network around the charging outcome.
From charger behaviour and session execution to energy, billing and roaming, Vampire.Energy is designed to give operators one operational view across the charging lifecycle.
See how deployments are commercially scoped arrow_forward