VDV 261 и VDV 463: Два стандарта, которые должен поддерживать каждый автобусный парк (и почему большинство из них этого не делают)

VDV 261 and VDV 463 are the two standards that decide whether your bus depot runs smoothly tomorrow morning — or whether a bus leaves cold, late, and half-charged.

Every morning, a bus has to leave the depot on time. Batteries full. Cabin warm. Ready for the first passenger. The driver doesn’t care which standard the charger speaks. But the depot operator does — because when VDV 261 and VDV 463 are missing from the charging software, things quietly break.

This guide is intended for professionals involved in the planning, procurement, and operation of bus depot charging infrastructure. By the end, you’ll know what VDV 261 and VDV 463 do, why they matter, and what to ask any Программное обеспечение для зарядки EV vendor before you sign.

 Загрузка ...

What VDV 261 and VDV 463 actually are

VDV 261 and VDV 463 are two communication standards from the Verband Deutscher Verkehrsunternehmen — the German Association of Transport Companies. They were built for one reason: to make electric bus depots work.

Think of it like this. A diesel depot is simple. A bus pulls in. Someone fills the tank. Job done. An electric bus depot is not simple. A bus pulls in. It needs to be charged. It needs to be warm or cool before the driver arrives. It needs to be ready by a specific time. Many buses arrive at once. Some leave earlier than others. Energy costs change through the day. The grid has limits.

VDV 261 and VDV 463 are how the depot’s brain talks to the chargers and the buses so all of this works at the same time. VDV 463 handles the link between the central depot systems and the charging management system. VDV 261 handles the link between the charging management system and the vehicle itself.

Together, they turn a depot full of separate machines into one coordinated operation.

Why VDV 261 and VDV 463 matter for bus depots

Here’s the thing most CMS vendors don’t tell you. An OCPP-only charging system can start and stop a charging session. That’s it. It doesn’t know the bus schedule. It doesn’t know which bus leaves first tomorrow. It doesn’t know how cold the cabin is. It doesn’t know when to pre-warm the battery so the bus can accept full power the moment it plugs in.

Without VDV 261 and VDV 463, depot teams fill those gaps by hand. Spreadsheets. Phone calls. Manual overrides. It works until your fleet grows past 20 buses. Then it starts to break. A bus leaves cold. Another sits at a charger it didn’t need. Energy bills climb because charging happens at peak hours instead of off-peak.

VDV 261 and VDV 463 remove those gaps. The depot system tells the charging system when each bus must leave and in what state. The charging system plans the energy and the pre-conditioning. The bus gets ready on time. Every time.

VDV 463 explained: how the depot talks to the charging system

VDV 463 is the upstream standard. It connects the depot’s planning systems — the ones that know tomorrow’s schedule — to the charging system. The two systems talk over WebSocket with JSON messages.

Here’s what that looks like in practice. The Depot Management System (DMS) or the Intermodal Transport Control System (ITCS) sends the charging system a request. The request says things like: “Bus 42 arrives at 22:15 tonight at charger 7. It leaves at 05:30 tomorrow. Charge it to at least 90%. Pre-warm the cabin before departure.” The charging system receives that. It plans the session. It reports back with status, battery state, energy used, and any errors along the way.

That’s the heart of VDV 463. One side says what the fleet needs. The other side says what’s happening. Both sides stay in sync all night long.

What makes VDV 463 different from OCPP

OCPP is the standard between the charging system and the charger. It’s essential. But OCPP is not aware of bus schedules. It doesn’t know when buses leave the depot. VDV 463 fills that gap. It’s the layer above OCPP. Any Система управления зарядными станциями EV built for buses needs both.

Рекомендуем прочитать:

Протоколы OCPP (OCPP 1.6, OCPP 2.0.1 и OCPP 2.1)

VDV 261 explained: how the charging system talks to the bus

VDV 261 is the other half of the story. It’s the standard between the charging management system and the vehicle itself. It runs over the ISO 15118 connection — the same one used for Plug and Charge.

VDV 261 is what makes pre-conditioning possible. Pre-conditioning means preparing the bus before the driver arrives. The battery gets warmed up in cold weather so it can accept fast charging and push out full power. The cabin gets heated or cooled so passengers are comfortable from minute one. The driver saves time because the bus is not sitting there thawing or cooling down.

Through VDV 261, the bus tells the charging system: “I’m here. My VIN is this. My battery is at 18%. I’ll need 12 minutes to pre-warm the battery and 8 minutes of cabin heating.” The charging system responds with: “Here’s when you leave. Here’s your target state of charge. Here’s when to start the HVAC.” The two stay in constant small-talk while the bus charges.

Without VDV 261, pre-conditioning either doesn’t happen or it happens by guessing. With VDV 261, it happens precisely and automatically.

VDV 261 and VDV 463 in a typical depot night

Let’s walk through a real example. It’s 22:10. Fleet operations has locked in tomorrow’s schedule. Through VDV 463, that schedule flows into the charging management system. The CMS now knows which bus goes where, how full each battery needs to be, and when each bus leaves.

Интеллектуальная зарядка EV: Раскрытие полного потенциала

Отправляя эту форму, Вы подтверждаете, что ознакомились с нашими
политика конфиденциальности.

Δ

At 22:15, bus 42 arrives at charger 7. Driver plugs in. OCPP tells the CMS the session started. Through VDV 261, the bus shares its VIN, current battery level, and estimated pre-conditioning needs.

The CMS plans. It knows bus 42 leaves at 05:30. It knows electricity is cheapest from 01:00 to 05:00. It knows the depot has a grid limit it can’t exceed. It charges bus 42 slowly at first, ramps up during cheap hours, and finishes just in time. At 05:00 it starts pre-heating the battery. At 05:15 it starts warming the cabin. At 05:30, bus 42 rolls out with a full battery, a warm cabin, and a driver who didn’t have to do anything special.

Meanwhile, the CMS is doing this for 80 other buses. All at the same time. That’s what VDV 261 and VDV 463 are for.

Why most EV charging software fails on VDV 261 and VDV 463

Here’s the uncomfortable truth. Most Компании по разработке программного обеспечения для зарядки электромобилей were built for public charging. Cars. Parking lots. Retail sites. They speak OCPP fluently. But VDV 261 and VDV 463 are not on their roadmap. Or they are — as a “coming soon” feature that’s been coming soon for two years.

A few reasons this happens. VDV is a European transport standard. Most CMS vendors are focused on broader markets. Building VDV support takes real engineering — WebSocket handshakes, JSON schemas, certificate management for ISO 15118, message sequence handling, timeout logic, pre-conditioning workflows. It’s not a weekend project. It’s months of work. And the customers who need it — depot operators — are not as loud in the market as public CPOs.

So when a depot operator runs a tender, what usually happens is this. Five CMS vendors reply. All claim “fleet-ready.” Three have never heard of VDV 463. One has it on a slide but not in production. One has actually built it. Telling the difference takes a few hard questions.

How to tell real VDV 261 and VDV 463 support from marketing claims

Here’s the one list I’ll use in this article — the questions to ask any vendor:

• Which VDV 463 message types do you support in production today? You’re looking for ProvideChargingRequest, ProvideChargingInformation, and BootNotification at minimum.
• Can I see your VDV 463 WebSocket endpoint in a sandbox? A vendor with real support can show you one. A vendor without it will change the subject.
• How do you handle VDV 261 pre-conditioning certificates? Real answer involves ISO 15118 certificate management, key stores, and renewal workflows.
• Which depot systems have you integrated with over VDV 463? Ask for names. Ask for reference calls.
• What happens when the ITCS sends a conflicting schedule update mid-session? A real vendor has a clear answer involving priority rules and device schedules.
• Do you support schedule-based charging and ad-hoc charging at the same time? Most operators need both.

If a vendor struggles with any of these, take it as a signal. VDV is the kind of thing you only truly understand once you’ve built it.

What good VDV 261 and VDV 463 support looks like

A charging management system that really supports VDV 261 and VDV 463 does a few specific things well.

It accepts charging requests from multiple depot systems at once. One depot might use a DMS. Another might use an ITCS. Some use both. The CMS handles all of them through clean profile and platform configuration.

It keeps a live connection. VDV 463 runs over WebSocket. That means the link stays open all night. Ping and pong messages keep it alive. If it drops, the CMS reconnects and catches up.

It reports back properly. The depot system doesn’t just want to send instructions. It wants to see what’s happening. Battery state. Energy delivered. Any charging faults. Pre-conditioning status. A good CPMS reports all of that on a configurable interval, not just when something breaks.

It respects the fleet’s priorities. When the depot says bus 42 is more important than bus 18, the CPMS honors that. When the grid is tight, it charges the priority buses first. When one bus is done, the energy flows to the next one in line. This is the kind of интеллектуальная зарядка EV VDV makes possible.

It handles pre-conditioning as a normal part of the workflow. Not as an afterthought. The bus’s pre-warming is planned alongside its charging. Both finish at the right time.

VDV 261 and VDV 463 beyond buses

One thing worth knowing. VDV was designed for buses first. But the standards apply equally well to any electric vehicle флот that runs on a schedule. Heavy-duty trucks at logistics depots. Refuse collection fleets. Municipal service vehicles. Airport ground support equipment.

Any fleet that arrives at a known time, needs to charge, and has to leave at a known time can benefit from VDV 261 and VDV 463. The principles are the same. Schedule in. Charging and pre-conditioning planned. Ready on time. Reported back.

This is why we built VDV 261 and VDV 463 support into Tridens EV Charge in a way that serves buses first but extends naturally to other heavy-duty use cases. One CMS. Many fleet types. Same standards under the hood.

Готовы приступить к работе?

Learn how your business can thrive with Tridens EV Charge for fleets.

Отправляя эту форму, Вы подтверждаете, что ознакомились с нашими
политика конфиденциальности.

Δ

What you gain when VDV 261 and VDV 463 work properly

Let’s be concrete about the business impact. When VDV 261 and VDV 463 are in place and working, depot teams stop firefighting. Dispatchers stop calling drivers to say “skip the second run, bus 14 isn’t ready.” Energy bills drop because charging shifts to cheap hours automatically. Cabin comfort improves because pre-conditioning is consistent, not manual. Fleet uptime goes up because fewer buses miss their first run.

These are not abstract benefits. They show up in the monthly operating report. Less overtime. Lower energy spend. Fewer service gaps. More driver satisfaction. A cleaner relationship between the depot and fleet operations.

And from an IT perspective, integration stops being a custom project. VDV 261 and VDV 463 are standards. You build once, you integrate many times. You don’t rewrite the interface every time you swap vendors or add a new depot.

How Tridens supports VDV 261 and VDV 463

We’ll be direct about this. Tridens EV Charge is a charge management system built for CPOs, EMSPs, и fleet operators. VDV 261 and VDV 463 support is engineered into the platform — not a slide.

On the VDV 463 side, the platform accepts charging requests from depot and transport control systems, tracks them as device schedules, and drives charger behavior based on those schedules. Reporting runs on a configurable interval back to the upstream systems. On the VDV 261 side, vehicle data flows through ISO 15118 into the platform, pre-conditioning requests flow back out, and everything stays in sync through the charging session.

We already work with a major European bus operator on exactly this setup. And we are rolling the same approach out to heavy-duty truck fleets and depot-based networks. If you want the details of that case — how the integration was designed, what the depot team saw in the first 90 days — we have it ready to share. Just ask.

FAQs about VDV 261 and VDV 463