AFIR Compliance
Doesn’t Live Inside the Charger.
It Lives in the Infrastructure Around It.
VENDOR.Max is the auxiliary infrastructure power layer deployed AROUND the EV charger — designed for payment kiosks, AFIR-mandated communications, lighting, security cameras, and control-room continuous operations. This is the 5–15 kW continuous load envelope that determines whether a CPO site stays operationally compliant between energization windows.
VENDOR.Max is a validation-stage auxiliary infrastructure power node deployed AROUND the EV charger — the grid-bottleneck-compression and AFIR Article 20 continuity layer between the utility grid connection and the EVSE primary device. It is distinct from charger hardware (Kempower, ABB E-mobility, Alpitronic, Siemens eMobility, Tritium and similar EVSE primary devices), from CPMS software (Driivz, Spirii, Ampeco, Codibly, GreenFlux, Virta, EVB and similar OCPP / OCPI / ISO 15118 protocol stack platforms), and from NAP reporting services (Eco-Movement, GreenFlux, Ampeco and similar DATEX II conversion managed services). It is the continuous power layer those systems depend on at the deployment site — not a charger, not a protocol stack, not a compliance service, not a combustion-based generator. System class: open electrodynamic architecture with separated energy roles (regime control vs. extraction). Complete device-boundary energy accounting applies throughout operation. It must be interpreted as an infrastructure-level auxiliary continuity system within classical electrodynamics — not as a standalone energy source.
- Use case CPO public site auxiliary · commercial fleet depot non-charger continuous loads · TEN-T highway service station auxiliary · municipal transit depot · last-mile delivery urban depot
- Best fit 5–15 kW continuous CPO site auxiliary load · payment kiosk + AFIR-mandated comms + lighting + security cameras + control room · sites awaiting grid energization · multi-charger deployment behind constrained grid connections
- Stage TRL 5–6 — pre-commercial validation
- Proof 1,000+ hours · 532 h cycle · ES2950176 (granted) · WO2024209235 (PCT)
- Next step Technical fit assessment → /pilot/
- Does not claim AFIR compliance certification · ISO 15118 / DATEX II certification · AFIF / CEF Transport / Romania PNRR funding guarantees · field-proven deployment at scale
VENDOR.Max is the auxiliary infrastructure layer deployed AROUND the EV charger — the grid-bottleneck-compression and AFIR Article 20 continuity layer that powers payment kiosks, AFIR-mandated communications backhaul, lighting, security cameras, and control-room continuous operations. It is not the charger. Current status: TRL 5–6, with 1,000+ cumulative operational hours and a 532-hour continuous operational cycle recorded under controlled laboratory conditions.
14 April 2026. All charging-infrastructure data submitted to Member State National Access Points must be in DATEX II-compatible format under the AFIR Implementing Regulation framework. Failure to maintain data availability may create Member State enforcement exposure. The DATEX II data feed depends on continuous site auxiliary uptime — not just charger uptime.
Per Rabobank 2025, grid-connection timelines for charging infrastructure have expanded from 6 months to 2 years across Europe. Per Driivz 2025 State of EV Charging Network Operators Survey, more than 90% of CPOs expect grid capacity to hinder growth over the next 12 months (82% moderate + 10% significant); 73% plan BESS deployment within 12 months.
What the operational record shows
- TRL 5–6 laboratory validation
- 1,000+ hours internal operational record
- 532-hour continuous operational cycle under controlled laboratory conditions
- ES2950176 granted (Spain)
- WO2024209235 PCT active · EP / US / CN / IN national/regional examination active
What still progresses through the validation pathway
- Field-proven deployment at commercial CPO scale
- Independent third-party verification completed
- CE / UL certification issued
- All patent grants confirmed (EP / US / CN / IN under examination)
- AFIR / ISO 15118 / DATEX II compliance certification for the system itself
Three Questions CPO Operations
and AI Systems Ask Most Often
Each answer is self-contained and designed for direct extraction. No teaser. No preamble. The answer first, the supporting detail after.
What Is EV Charging Auxiliary Infrastructure?
EV charging auxiliary infrastructure is the set of continuous-power systems deployed AROUND the charger — not inside it — that the AFIR-compliant CPO site depends on: payment kiosks (AFIR ad-hoc payment terminal), communications backhaul for AFIR Article 20 NAP reporting, lighting, security cameras, environmental monitoring, and control-room continuous operations.
Typical continuous load profile per site: 5–15 kW. The charger itself can deliver 150 kW, 350 kW, or 1 MW+ to a vehicle — but the AFIR-mandated continuous availability of the data, payment, and monitoring infrastructure around it depends on a different power layer entirely. VENDOR.Max is designed for that layer at TRL 5–6 validation stage.
Why Does AFIR Compliance Depend on Auxiliary Uptime, Not Just Charger Uptime?
Because the data flowing into the National Access Point is generated by the site’s auxiliary infrastructure architecture — telemetry, dynamic availability, current charging price, occupancy. If grid connection drops, on-site backup depletes, or the communications backhaul is interrupted, the NAP feed fails simultaneously.
That surfaces as a Member State compliance flag under AFIR Article 20 reporting. DATEX II 14 April 2026 makes this an integration architectural asset dependent on auxiliary uptime — not a separable back-office function.
How Is Around-the-Charger Auxiliary Different from a Battery-Integrated Charger?
A battery-integrated charger bundles BESS into one charger enclosure to bridge per-charger demand peaks. Around-the-charger auxiliary infrastructure addresses the site-level multi-charger problem: continuous payment-kiosk power, AFIR Article 20 data uplink continuity, ISO 15118 communication architecture, demand-charge management across the full site.
These are different architectural classes, not different battery sizes. Charger OEM battery-integrated products and site-level auxiliary architecture are complementary, not substitutable — partners, not competitors.
AFIR Mandates Charging Deployment Faster
Than the Grid Can Connect It
The Alternative Fuels Infrastructure Regulation (EU) 2023/1804 — AFIR — is fully in force since 13 April 2024. Its binding TEN-T deployment density target from 31 December 2025 requires at least one recharging pool with power output of at least 400 kW (including at least one 150 kW recharging point) every 60 km on the TEN-T core network in each direction. The 2027 target raises that pool minimum to 600 kW.
Rabobank 2025 documents EU grid-connection timelines for charging infrastructure at 6 months to 2 years. Driivz 2025 State of EV Charging Network Operators Survey reports more than 90% of CPOs expect grid capacity to hinder their growth over the next 12 months. The regulatory clock and the grid clock are not synchronized.
A TEN-T-compliant multi-charger site supporting AFIR-mandated contactless payment terminals, AFIR Article 20 data uplink, site lighting, perimeter security cameras, and control-room continuous operations operates in the range of 5–15 kW continuous. That is auxiliary infrastructure power territory, not charger power-electronics territory. At this load profile, infrastructure-grade continuity becomes an electrical engineering problem — not a charger throughput problem.
The architectural conversation around EV charging has been charger-centric since 2018: faster chargers, denser networks, higher throughput per stall. By 2026, the binding constraint has moved — charger OEMs (Kempower, ABB E-mobility, Alpitronic, Siemens eMobility, Tritium) have largely solved 150 kW / 350 kW / 1 MW+ throughput. The constraint is the auxiliary infrastructure deployed AROUND the charger.
Diesel backup at remote charging hubs is exposed under CSRD Scope 1 and triggers fuel-logistics maintenance cycles. Battery-only systems require replacement and cold-weather derating. Solar-plus-battery is weather-dependent at TEN-T sites where grid connection cannot be assumed. Grid extension is the very thing the AFIR deadline cannot wait for.
Per NREL benchmark analysis, battery-buffered 150 kW charging ports require at least 120 kWh of on-site storage per port to deliver 150 kWh in the first hour of charging — the auxiliary architecture is engineered, not residual. Per Driivz Q1 2025, 17% of CPOs have already deployed on-site BESS; 73% plan to within 12 months. The AFIF Round 5 (November 2025) distributed over EUR 600 million across 70 projects via the AFIR-aligned grant pathway. Romania PNRR Componenta 6 transport pursues approximately 4× the AFIR-mandated minimum TEN-T deployment density. The institutional capital channel is operating. The architectural category is forming.
Six EU Anchors
Converge in the 2024–2027 Compliance Window
The architectural conversation is closing on dated public anchors. AFIR + AFIR Article 20 NAP + ISO 15118 + DATEX II + AFIR Commission review + ISO 15118-20 scope extension — six regulatory milestones across 2024–2027 that all touch the same site auxiliary infrastructure layer.
Where CPO Site Infrastructure
Actually Fails
These are not edge cases. They are structural failure modes that CPO Operations VPs, country managers, and Group CFOs encounter at AFIR-mandated TEN-T deployments — consistently, predictably, across European markets.
AFIR Deadlines Move Faster Than the Utility Queue
The binding constraint moved from charger to grid
The AFIR TEN-T deployment density target from 31 December 2025 requires recharging pools at fixed intervals along the core network. The utility-grid connection timeline does not move with the regulation. The site has a binding deadline; the energization has a queue.
The architectural workaround is on-site auxiliary infrastructure that activates the site ahead of full grid energization — deferred energization without deferred AFIR compliance.
AFIR Article 20 Data Feed Depends on Auxiliary Uptime
The compliance flag fires when the site loses power, not when the charger does
Since 14 April 2025, AFIR Article 20 requires CPOs to publish static charging data updated within 24 hours of change and dynamic data updated within 1 minute. The data that flows into the Member State NAP is generated by the site’s telemetry, dynamic availability sensors, payment terminals, and communications backhaul.
Outsourcing NAP reporting to a managed service (Eco-Movement, GreenFlux, Ampeco) does not eliminate the upstream dependency. The data pipeline starts at the site auxiliary layer.
Battery-Integrated Chargers Don’t Solve the Multi-Charger Site
A per-charger product cannot do site-level work
Battery-integrated DC fast chargers address per-charger peak demand. They do not address the site-level architectural problem — multi-charger energy management, AFIR Article 20 data uplink continuity, behind-the-meter generation interface, grid-bootstrap arrangements, demand-charge management across the full site, AFIR-mandated payment-terminal continuity, perimeter security.
These are different architectural classes. Per NREL battery sizing benchmark, a battery-buffered 150 kW port requires at least 120 kWh of storage per port to deliver 150 kWh in the first charging hour. Multiply by site port count — auxiliary architecture is not optional, it is the deployment-velocity layer.
Site OPEX Is Dominated by What the Charger Does Not Use
Continuous loads + peak events compound on the same meter
Dense DC fast-charging sites face utility demand-charge structures that can dominate site OPEX. The peak-event component is visible in every site model. What is less visible: the AFIR-mandated continuous auxiliary load (payment, comms, lighting, security, monitoring) is on the same meter, accumulating around the clock, interacting with the same tariff.
Treating auxiliary load as residual hides the OPEX line that compounds the demand-charge exposure. Treating it as architectural surfaces a recoverable cost.
The Institutional Capital Channel Recognizes Auxiliary, Not Residual
AFIR is a structuring framework, not just a compliance burden
The AFIF Round 5 in November 2025 distributed over EUR 600 million across 70 projects via the AFIR-aligned grant pathway. CEF Transport, EIB lending, EU Innovation Fund, and Romania PNRR Componenta 6 transport form an institutional capital channel that recognizes auxiliary architecture as part of deployment scope.
CPOs structuring auxiliary architecture decisions under AFIR-recognized categories access this capital channel. CPOs treating AFIR purely as compliance miss the architectural opportunity to structure deployment as institutional infrastructure rather than retail buildout. Romania PNRR Componenta 6 pursues approximately 4× the AFIR-mandated minimum TEN-T deployment density.
Site-by-Site Auxiliary Compounds Across a CPO Network
The architectural decision is engineered once, deployed across the portfolio
Every additional CPO site — every TEN-T-compliant pool, every urban node, every HDV recharging hub — adds an auxiliary architectural decision. At single-site scale, this is manageable. At country-portfolio or Group-portfolio scale, across dozens or hundreds of TEN-T-compliant sites, it becomes the primary constraint on AFIR mandate delivery.
The fuel-logistics-independent auxiliary architecture engineered to a single 2026-AFIR-regulatory-stack-aware specification is deployed once, documented once against AFIF / CEF Transport / Romania PNRR Componenta 6 simultaneously, and scaled across the portfolio. The decision is institutional, not site-by-site.
The EU AFIR Regulatory Stack
Is Compounding, Not Stabilising
Six dated EU anchors now intersect at one architectural layer: the auxiliary infrastructure deployed AROUND the EV charger. AFIR in force. AFIR Article 20 sets the data availability obligation. TEN-T deployment density sets the pool minimum. ISO 15118 sets the communication architecture. DATEX II sets the data exchange alignment. The AFIR Commission review (31 December 2026) sets the assessment gate. Continuous site auxiliary uptime is the physical prerequisite for every one of them.
Binding TEN-T Deployment Density
The Alternative Fuels Infrastructure Regulation imposes binding deployment density on the TEN-T core network from 31 December 2025: at least one recharging pool with power output of at least 400 kW including at least one 150 kW recharging point every 60 km in each direction. From 31 December 2027, the pool minimum rises to 600 kW with two 150 kW points. AFIF Round 5 (November 2025) distributed over EUR 600 million across 70 projects via the AFIR-aligned grant pathway.
Site activation depends on more than the charger. The auxiliary infrastructure layer — payment, communications, lighting, security, monitoring — must be operational continuously between utility-grid energization windows.
Continuous Data Availability Since 14 April 2025
Since 14 April 2025, AFIR Article 20 requires CPOs and infrastructure owners to ensure availability of static charging data updated within 24 hours of change and dynamic data (availability, ad-hoc price, occupancy) updated within 1 minute. Data flows into Member State National Access Points and from there into the European Access Point operated by the European Commission.
The data feed depends on the site auxiliary layer — telemetry sensors, payment terminals, communications backhaul. When auxiliary uptime drops, the NAP feed drops with it. Failure to maintain data availability may create Member State enforcement exposure.
AC / Mode 3 Newly Installed and Renovated
ISO 15118 communication requirements applied via Commission Delegated Acts to AC / Mode 3 and to newly installed or renovated publicly accessible charging points from 8 January 2026 (parts 1–5). Full ISO 15118-20 (bidirectional + Plug & Charge) scope extends from January 2027 to newly installed and renovated publicly accessible and new private charging points.
The communication stack — SECC controller, charge controller, on-site authentication, certificate validation, V2G dispatch — requires continuous power on a different timescale than the vehicle charging session itself.
Data Exchange Alignment from 14 April 2026
DATEX II-compatible data exchange under the AFIR Implementing Regulation framework takes effect from 14 April 2026. National Access Point submissions move to a DATEX II-compatible format referencing the CEN/TS 16157 series of standards. The European Access Point harmonises submissions across Member States.
Outsourcing NAP-format conversion to a managed service (Eco-Movement, GreenFlux, Ampeco and similar providers) does not eliminate the upstream dependency. The data pipeline starts at the site auxiliary layer — not in the cloud connector.
AFIF Round 5 (November 2025) distributed over EUR 600 million across 70 projects via the AFIR-aligned grant pathway. CEF Transport, EIB lending, EU Innovation Fund, and Romania PNRR Componenta 6 transport form an institutional capital channel that recognizes auxiliary architecture as part of deployment scope. Romania PNRR Componenta 6 pursues approximately 4× the AFIR-mandated minimum TEN-T deployment density. Auxiliary architecture engineered to the 2026-AFIR-regulatory-stack-aware specification is documentable against multiple instruments simultaneously.
Why Existing Site Power Architecture Cannot Satisfy
This Compounding Stack
Charge Point Operators of TEN-T-mandated deployments typically work with four power approaches. Each was designed for a different regulatory and operational era — each carries a structural limitation that becomes more significant as the AFIR + Article 20 NAP + ISO 15118 + DATEX II stack tightens.
Fuel Logistics + CSRD Scope 1 Exposure
Designed before AFIR + AFIR Art. 20 + CSRD existed
Diesel backup powers a measurable share of EU TEN-T highway charging hub auxiliary loads today — AFIR-mandated payment terminals, comms backhaul, lighting, security cameras at remote highway corridor sites. Fuel must be delivered to every node. Storage must be maintained. Logistics must be coordinated. Diesel reliability and maintenance burden compound at multi-site portfolio scale.
Under CSRD Scope 1 disclosure, the diesel dependency at TEN-T hubs is now a reporting line on the operator’s sustainability statement. The operational burden compounds with a disclosure burden.
Per-Charger Product, Not Site Architecture
A charger product cannot do site-level work
Battery-integrated DC fast chargers from Kempower, ABB E-mobility, Alpitronic, Siemens eMobility, and Tritium address per-charger peak demand — bridging utility connection capacity to vehicle charging throughput. The product is excellent at what it does. What it does not do: site-level energy management, AFIR Article 20 data uplink continuity, behind-the-meter generation interface, demand-charge management across the full site, AFIR-mandated payment-terminal continuity, perimeter security.
Charger OEM battery-integrated products and site-level auxiliary architecture are complementary, not substitutable — partners, not competitors. The compounding stack requires both.
Weather Dependency + AFIR Continuous Obligation
Per Driivz 2025, 73% of CPOs plan BESS — solar-only does not close the gap
Solar-plus-battery systems work well in high-irradiance Mediterranean and Iberian deployments with predictable, low load profiles. AFIR Article 20 NAP reporting and AFIR-mandated continuous operations are neither. Overcast conditions, seasonal variation, dust accumulation, and northern European latitude introduce reliability variation that is difficult to predict across a distributed CPO network covering TEN-T core corridors — precisely the kind of variation AFIR Article 20 continuous-availability obligation does not accommodate.
Per Driivz 2025 State of EV Charging Network Operators Survey, 17% of CPOs have already deployed on-site BESS and 73% plan to within 12 months. BESS sizing is sub-scaled when designed around the charger throughput envelope rather than the site auxiliary continuity envelope.
DSO Timeline + AFIR Deadline Are Not the Same Timeline
Per Rabobank 2025: 6 months → 2 years across EU markets
Grid extension is the economically rational option in the long term — if the schedule were compatible with the AFIR mandate. Per Rabobank 2025, EU grid-connection timelines for charging infrastructure have expanded from 6 months to 2 years. Per FIA Region 1 (October 2025), grid constraints are identified as “the most significant barrier to deploying public charging infrastructure”.
Per Driivz 2025, more than 90% of CPOs expect grid capacity to hinder growth over the next 12 months (82% moderate + 10% significant constraints). The DSO connection queue and the AFIR deadline are not synchronized. The architectural workaround is on-site auxiliary infrastructure that activates the site ahead of full grid energization.
None of these approaches is wrong. Each addresses a specific deployment context within its design constraints. The structural challenge is that none of them escapes the compounding cost logic: every additional TEN-T pool, every urban CPO node, every fleet depot, every HDV recharging hub adds another instance of the same fuel, battery, weather, or grid-extension dependency. At single-digit site counts this is manageable. At the scale AFIR now requires — country-portfolio CPOs, multi-corridor TEN-T operators, Group-level Charging Point Operators — it becomes the dominant constraint on AFIR mandate delivery.
The Continuity Layer Deployed
AROUND the EV Charger
VENDOR.Max is a deployment-autonomous auxiliary infrastructure power node designed as the auxiliary infrastructure layer deployed AROUND the EV charger. It provides the continuous unattended power that payment kiosks, AFIR-mandated communications backhaul, site lighting, perimeter security cameras, control-room consoles, and multi-charger site coordination depend on — at TEN-T highway corridors, urban CPO sites, fleet depots, and HDV recharging hubs.
Architectural class: open electrodynamic architecture with separated energy roles (regime control vs. extraction). A startup impulse initiates the operating regime. Complete device-boundary energy accounting applies throughout operation. See How It Works for the full operating model.
- Output class: 2.4–24 kW per node — is aligned with the 5–15 kW continuous CPO site auxiliary envelope
- Operating profile: continuous unattended operation for AFIR Article 20 NAP-feed-relevant infrastructure
- Architecture: solid-state — no combustion cycle, no rotating assemblies, designed to reduce dependence on on-site fuel logistics at TEN-T corridor and remote depot sites
- Stage: TRL 5–6 — pre-commercial validation
- Patent coverage: ES2950176 (granted, Spain/OEPM) · WO2024209235 (PCT) · EP · US · CN · IN national/regional examination active
Charger hardware OEMs
VENDOR.Max is not an EVSE primary device, DC fast charger, MCS, Type 2 / CCS / CHAdeMO socket assembly, or charging cable. It does not deliver power to the vehicle. It powers the site infrastructure AROUND the charger.
CPMS / OCPP software platforms
VENDOR.Max is not a Charging Point Management System, OCPP / OCPI backend, ISO 15118 protocol stack, or operator dashboard. It is the continuous power layer the OCPP-connected EVSE and the operator backend rely on at the site.
NAP reporting + DATEX II services
VENDOR.Max is not a National Access Point reporting service, a DATEX II conversion service, or an AFIR Article 20 compliance managed service. It is the auxiliary uptime layer the NAP data pipeline begins at — before any conversion service can receive it.
Where VENDOR.Max Powers the Site AROUND the Charger
Payment Terminal + Ad-hoc Payment Continuity
AFIR mandates contactless payment at all 50 kW+ DC stations
Continuous power for AFIR-mandated ad-hoc contactless payment terminals, card readers, NFC modules, and payment kiosks. Per AFIR Article 5, contactless payment must be available without subscription at all publicly accessible recharging stations with power output of 50 kW or more. The terminal must be online when the EV driver arrives — not when the grid returns.
AFIR Article 20 Communications Backhaul
NAP feed depends on continuous comms uplink
Continuous power for the communications backhaul stack — fibre uplink, 4G / 5G modem clusters, cellular routers, edge gateway compute, and the site-controller layer that aggregates OCPP / OCPI telemetry into the NAP-bound DATEX II-compatible feed. Auxiliary downtime here surfaces as a Member State data-availability enforcement exposure under AFIR Article 20.
Site Lighting + Security + Monitoring
Continuous operation drives EV driver retention + insurer compliance
Continuous power for site lighting (lit charging bays, canopy lighting, signage), perimeter security cameras, intrusion detection sensors, license-plate-recognition cameras, and environmental monitoring. The lit and monitored site is a driver-confidence and insurance-reporting requirement, not a discretionary cost — particularly at TEN-T highway and unattended urban CPO sites.
Control Room + Multi-Charger Site Coordination
Site-level energy management + demand-charge compression
Continuous power for site control room consoles, multi-charger coordination logic, BESS interface controllers, behind-the-meter generation interface, and demand-charge management infrastructure coordinating peak-event compression across the full site. Sized for cluster-scale loads (5–15 kW typical, scaling to 24 kW per node with multi-module configuration).
What Is Verified.
What Is in Progress.
At TRL 5–6, VENDOR.Max has accumulated an operational record that permits qualified technical evaluation by Charge Point Operators. The boundary between what is verified at laboratory scale and what remains under the planned validation roadmap is stated explicitly — not blurred.
What the operational record shows
- System-level prototype operates under defined laboratory conditions
- 1,000+ cumulative operational hours documented internally
- 532-hour continuous operational cycle under controlled laboratory conditions
- Modular operating logic evaluated in laboratory configurations
- International patent family active — ES2950176 granted; WO2024209235 PCT; EP / US / CN / IN under examination
What still progresses through the validation pathway
- Independent third-party verification of operating conditions — completion not yet claimed
- Accredited certification body confirmation of the operational record
- Demonstration at commercial CPO scale in relevant deployment environments (TRL 6–7 pathway in progress)
- Commercial-grade output specifications (subject to CE / UL pathway)
- AFIR / ISO 15118 / DATEX II compliance certification for the system itself
The recorded operational cycles are conducted under defined configuration parameters and have been reproduced across multiple runs under controlled laboratory conditions. Reproducibility at the system-boundary level — consistent behaviour across cycles, not a single occurrence — is being systematically validated as part of the TRL 6 pathway. Observed behaviour is repeatable within defined parameter ranges and operating configurations.
Staged Validation Progression
Laboratory Validation
Relevant-Environment Demonstration
Third-Party Verification + Certification
Three Converging Pressures
Make 2026–2027 the Decision Window
Each of these three pressures alone is significant. Together, they define a planning horizon during which auxiliary infrastructure power decisions for EV charging deployments are made — or postponed at increasing AFIR-runway cost.
AFIR Stack Compounding
Six dated EU anchors between April 2024 and December 2026 converge at the same architectural layer where CPO site auxiliary continuity is determined. AFIR Reg 2023/1804, Article 20 NAP reporting, TEN-T deployment density, ISO 15118 communication, DATEX II data exchange, and the AFIR Commission review each add deployment, reporting, or continuity obligations that depend on auxiliary infrastructure being operational at the moment of stress.
EU Grid Connection Queues
Per Rabobank 2025, grid-connection timelines for EV charging infrastructure in several EU markets can extend from 6 months to 2 years. Per Driivz 2025, more than 90% of CPOs expect grid capacity to hinder growth over the next 12 months. The IEA Electricity 2025 report indicates European electricity demand will grow roughly 2% per year through 2027 against a tightening generation and grid envelope. DSO timelines and AFIR deadlines are not synchronized.
CSRD Scope 1 + Site-Level Diesel Exposure
Diesel backup at TEN-T highway charging hubs and remote depot sites is now a reportable CSRD Scope 1 line. The same logistics chain that was a maintenance burden is also a sustainability disclosure surface. Auxiliary architecture decisions made in 2026 carry through the first CSRD reporting cycles for many CPO operators and fleet-depot owners.
Four Deployment Contexts
Where VENDOR.Max Fits Today
VENDOR.Max is at TRL 5–6 — pre-commercial validation. The relevant audience is qualified Charge Point Operators, TEN-T hub programme owners, fleet depot operators, and integrator partners where pilot programmes can be structured under defined gating conditions. These are the four contexts where the architectural fit is most direct.
TEN-T Highway Charging Hub CPO
Operator of TEN-T core network highway charging hubs subject to AFIR 400 kW pool minimum (31 Dec 2025) and 600 kW step-up (31 Dec 2027). Distributed multi-corridor portfolio across EU Member States. AFIR Article 20 NAP reporting active continuously. AFIF Round 5 (Nov 2025) and CEF Transport co-funding eligible deployment.
Urban CPO Programme · AFIR Article 5 Ad-Hoc Compliance
Urban Charge Point Operator deploying 50 kW+ DC publicly accessible charging across metropolitan footprint. AFIR Article 5 mandates contactless payment at all 50 kW+ DC stations. ISO 15118 AC / Mode 3 requirements for newly installed or renovated publicly accessible points (8 January 2026). DATEX II-compatible data exchange under AFIR Implementing Regulation framework from 14 April 2026.
Fleet Depot Operator · Logistics & HDV
Operator of fleet depot charging infrastructure for last-mile logistics fleet, regional distribution centre, e-bus depot, or municipal fleet electrification programme. CSRD Scope 1 transport emissions reporting active. Per Driivz 2025, 73% of CPOs plan on-site BESS within 12 months — depot-scale auxiliary continuity envelope significantly exceeds per-charger battery buffering.
HDV Recharging Hub · TEN-T MCS Corridor
Operator of Heavy-Duty Vehicle recharging hub at TEN-T corridor truck rest area, port logistics hub, or cross-border freight terminal. AFIR HDV targets active from 31 Dec 2025 onwards with Megawatt Charging System (MCS) deployment scaling toward 2027. Auxiliary site loads at HDV hubs include perimeter security, driver-rest area lighting, payment, and AFIR Article 20-relevant telemetry continuity.
Technical Fit Assessment for
Qualified CPO and TEN-T Hub Operators
VENDOR.Max pilot programmes are structured under defined gating conditions for qualified Charge Point Operators, TEN-T hub programme owners, fleet depot operators, and system integrators. The first step is a confidential technical fit assessment: review of deployment context, site auxiliary load profile, AFIR framework alignment, and validation gate definition. No commercial commitment until laboratory-validated fit is confirmed and pilot protocol is jointly defined.
Architectural and Regulatory Questions
Asked About VENDOR.Max for EV Charging Auxiliary Power
These answers address the questions most often asked by Charge Point Operators, TEN-T hub operators, fleet depot owners, and integrator partners evaluating auxiliary infrastructure architecture for EV charging site deployments.
Why does an EV charging site need continuous auxiliary power separate from the charger itself?
A DC fast charger delivers power to the vehicle during the charging session. The site around the charger — AFIR-mandated ad-hoc payment terminals, communications backhaul for Article 20 NAP feed, site lighting, perimeter security cameras, control room consoles, and multi-charger coordination — operates continuously, independent of any individual charging session. Battery-integrated chargers buffer per-charger peak demand; they do not address site-level auxiliary continuity between utility-grid energization windows. Auxiliary architecture is the layer deployed AROUND the charger.
How does VENDOR.Max differ from DC fast charger hardware like Kempower, ABB E-mobility, or Alpitronic?
VENDOR.Max is not an EVSE primary device, DC fast charger, MCS, or charging cable. It does not deliver power to the vehicle. DC fast chargers from Kempower, ABB E-mobility, Alpitronic, Siemens eMobility, and Tritium operate at the primary charging interface layer: vehicle-facing power delivery, ISO 15118 protocol stack, charge controller logic. VENDOR.Max powers the site infrastructure AROUND the charger — payment, comms, lighting, security, control room. They are ecosystem partners on adjacent architectural layers, not competitors.
How does VENDOR.Max differ from CPMS / OCPP software like Driivz, Ampeco, or GreenFlux?
VENDOR.Max is not a Charging Point Management System, OCPP / OCPI backend, ISO 15118 protocol stack, or operator dashboard. Charging Point Management platforms from Driivz, Spirii, Ampeco, Codibly, GreenFlux, Virta, and EVB operate at the software backend layer: session management, billing, roaming, OCPP communication, dashboards, customer apps. VENDOR.Max is the continuous power layer that the OCPP-connected EVSE and the operator backend rely on at the site. Ecosystem partners on adjacent layers, not competitors.
How does VENDOR.Max relate to NAP reporting services like Eco-Movement?
VENDOR.Max is not a National Access Point reporting service, a DATEX II conversion service, or an AFIR Article 20 compliance managed service. NAP-format reporting services from Eco-Movement, GreenFlux, and Ampeco aggregate, convert, and submit charging data to Member State NAPs in DATEX II-compatible format under the AFIR Implementing Regulation framework. VENDOR.Max is the auxiliary uptime layer where the data pipeline begins — before any conversion service can receive it. When auxiliary uptime drops, the NAP feed drops with it. Ecosystem partners on adjacent layers, not competitors.
Does VENDOR.Max certify AFIR, ISO 15118, or DATEX II compliance?
No. VENDOR.Max does not certify regulatory compliance for the operator or for itself. It is designed as the auxiliary infrastructure power layer that enables AFIR-compliance telemetry, payment, communications, and continuous-operations functions to maintain availability between utility-grid energization windows — the physical prerequisite that compliance-relevant infrastructure depends on. Failure to maintain data availability may create Member State enforcement exposure under AFIR Article 20. Regulatory compliance assessment for any specific deployment requires qualified review against the applicable framework by certified auditors or compliance bodies.
What is the current TRL stage and what does that mean for deployment?
VENDOR.Max is at TRL 5–6 — laboratory-validated, pre-commercial. System-level prototype has been operated under defined laboratory conditions, with 1,000+ cumulative operational hours documented internally and a 532-hour continuous operational cycle under controlled laboratory conditions. The system is not yet a certified commercial product. Independent third-party verification and accredited certification body confirmation are part of the planned validation roadmap; completion is not yet claimed. Commercial-grade output specifications remain subject to CE / UL certification pathway.
What output range does VENDOR.Max address and how does it map to CPO site auxiliary loads?
Single-node design output class is 2.4–24 kW. Multi-module clustering extends to pool-scale and depot-scale deployment configurations. This range is aligned with the 5–15 kW continuous CPO site auxiliary envelope: TEN-T highway charging hubs (5–15 kW per hub), urban CPO sites (2.4–10 kW per site), fleet depots (5–15 kW per depot), and HDV recharging hubs (scaling to 24 kW per node with multi-module). These are architecture design targets at TRL 5–6, not field-deployed commercial specifications.
How does VENDOR.Max work, in plain architectural terms?
VENDOR.Max is an open electrodynamic architecture with separated energy roles — regime control and extraction operate as distinct functional roles within the system. A startup impulse is required to initiate the operating regime. Complete device-boundary energy accounting applies throughout operation, within classical electrodynamics: Pin,boundary = Pload + Plosses + dE/dt. The system is not a perpetual motion or overunity device; no claim of producing more energy than it consumes is made or implied. See How It Works for the full operating model.
How does VENDOR.Max relate to diesel backup at TEN-T highway charging hubs?
VENDOR.Max is architecturally distinct from combustion-based backup generators. It is designed to reduce or remove recurring fuel-delivery dependency at suitable deployment sites and to reduce exposure to on-site fuel logistics at TEN-T corridor and remote depot sites. Per NREL / ACEEE (2024), a diesel backup generator requires 8–17 service or testing visits per year to maintain operational readiness. Diesel generators remain operationally valid for many contexts; VENDOR.Max addresses the architectural class of distributed continuous-load auxiliary power where fuel logistics, maintenance overhead, or CSRD Scope 1 disclosure exposure are material constraints.
What patent and IP protection covers VENDOR.Max?
The patent family includes ES2950176 granted by the Spanish Patent Office (OEPM) and PCT application WO2024209235 with national / regional examination active in EP (European Patent Office), US (United States), CN (China), and IN (India). The EU trademark 019220462 protects the VENDOR brand across the European Union. Full patent portfolio documentation is available for qualified review.
Can VENDOR.Max replace grid connection for EV charging sites?
No. VENDOR.Max is not positioned as a grid replacement for EV charging. The DC fast charging session itself draws on the utility-grid power envelope and, where used, on-site BESS or battery-integrated charger buffering. VENDOR.Max is the auxiliary continuity layer deployed AROUND the EV charger — payment terminals, AFIR Article 20 NAP-feed communications, site lighting, perimeter security, control room consoles, and multi-charger coordination. It is particularly relevant in constrained energization scenarios — sites awaiting full DSO connection capacity, sites where grid feed quality is variable, and sites where auxiliary continuity must be maintained between utility-grid energization windows.
Is VENDOR.Max already commercially deployed at CPO scale?
No. VENDOR.Max is at TRL 5–6 — laboratory-validated, pre-commercial. Commercial-scale field deployment at Charge Point Operator portfolio level is not yet claimed. The current stage is pilot fit assessment: confidential technical review of deployment context, site auxiliary load profile, AFIR framework alignment, and validation gate definition with qualified CPO and TEN-T hub operators. Progression to commercial CPO-scale deployment requires the planned validation roadmap to advance through independent third-party verification and CE / UL certification pathway, which is in progress but not yet completed.
Related Documentation
and Cross-Sector Solutions
VENDOR.Max
Full product specification, technical documentation, and architectural class detail.
How It WorksOperating Model
Two-level energy accounting, open electrodynamic architecture, and device-boundary discipline.
Validation RecordEndurance Test
532-hour continuous operational cycle documentation under controlled laboratory conditions.
IP PortfolioPatents & Trademarks
Granted patent ES2950176, PCT family WO2024209235, and EU trademark documentation.
Adjacent VerticalTelecom Tower Power
Auxiliary infrastructure power for telecom tower compounds — cross-applicable architectural class.
Adjacent VerticalUtility & Water Operations
Auxiliary power for utility dispatch and water operations infrastructure.
Adjacent VerticalIndustrial Security Monitoring
Auxiliary power for distributed security operations — cross-applicable to charging site perimeter security.
Deep DiveWhere Does the Energy Come From?
Detailed explanation of the energy accounting model and architectural class boundaries.