The category, plainly
The term covers a wide range of software, from models of finished buildings to systems wired into live sensors. Here's what the category actually means, the three shapes it comes in, where BEV Ready sits, and, just as plainly, what it doesn't do.
A digital twin is a working software model of a physical thing (a building, a piece of infrastructure, a workflow) that stays connected to real data about how that thing behaves or is planned to behave. You change parameters in the software; you see how the physical thing would respond.
The purpose isn't visualization for its own sake. A digital twin is a place to think out loud with data. You test what would happen if you added chargers, changed schedules, hit a bad-weather day or lost a piece of equipment, and you get back a defensible answer at a fraction of the time and cost of finding out on the physical thing itself.
Digital twins come in three broad shapes, distinguished by what they model:
BEV Ready is a process-simulation twin, applied to EV depot planning. The workflow it models is your depot's charging day, at 15-minute resolution. You change parameters (fleet size, vehicle types, charger count and power, service capacity, tariff) and see how the day would run against the site's real electrical and energy limits.
The free feasibility check is live now. The rest is the engineer-led depot twin, built with you and owned by you.
Today's tool answers the planning questions: what should this depot look like, and what will it take? Once a site is built and operating, a different set of questions takes over, and the roadmap addresses these deliberately, in the same observe-model-advise shape as the planning tool.
Everything in this section is on the roadmap. None of it is a live product feature today. We'll say plainly which pieces are being built now and which are further out.
A note on what the operations layer is NOT. Even at the roadmap horizon, BEV Ready remains a planning and analysis tool: an independent model that tells you whether your depot's operations are running the way they were designed to. It observes and advises; it does not control chargers, dispatch vehicles, or connect to your energy-management system in real time. That boundary is deliberate. The value is being the independent second opinion on what's actually happening, not another piece of software running your depot.
Being explicit about what a tool isn't is how technical buyers know it can be trusted for what it is.
Start with a free feasibility check, or talk through your depot with an engineer for 30 minutes.