EV Charging Tender CPMS Specification: An Installer's Guide

An EV charging tender’s CPMS section typically requires OCPP 1.6-J compliance, TLS-secured WebSocket communications (wss), dynamic load management under EPBD Article 14, RFID authentication, real-time energy reporting, and integration with stations from multiple hardware vendors. Most disqualifications come from missing load management or unverifiable security claims.

An installer in our customer base had the chance to install stations at a major client. The client made software a hard tender requirement: without a CPMS to include in the proposal, the installer would have been disqualified outright. With ELVO, they demonstrated full coverage of the technical requirements, including dynamic load management. They won the bid. The client also asked them to integrate existing stations from a previous vendor under the same platform.

If you are already working on a tender response this week, ELVO’s 30-day free trial gives you a working CPMS to reference in your proposal in under 5 minutes.

What an EV charging tender typically requires

EV charging tenders fall into two structural categories: public tenders (driven by EU AFIR Article 5 requirements for publicly accessible stations) and private tenders (driven by building-owner or fleet-operator needs under EPBD Article 14 and client-specific requirements). Both share six core technical requirements your CPMS must cover.

Public tenders (municipality, motorway, public parking, fleet operator) are governed by AFIR Article 5, which mandates contactless payment, real-time data publication, and OCPP-compliant communication for publicly accessible stations. These are hard requirements with audit consequences.

Private tenders (office building, hotel, mall, residential complex) are driven by EPBD Article 14 load management obligations plus client-specific concerns: RFID for tenant access, energy cost recovery, and integration with existing infrastructure. These are more variable, but TLS via wss and load management remain baseline.

The table below lists the six requirements that consistently appear across both categories and where you anchor your evidence:

Requirement	What it means concretely	Where to point evidence
OCPP compliance	OCPP 1.6-J Full (most current tenders) or 2.0.1 (large public tenders)	OCA registry: openchargealliance.org/certified-companies/
Secure communications	TLS via WebSocket Secure (wss) certificate	Vendor’s OCPP certification documentation
Dynamic load management	Real-time load balancing across active sessions per EPBD Article 14	EPBD Article 14 text (EUR-Lex) + vendor capability documentation
RFID authentication	User identification at charging point	Vendor support for ISO 15693 / Mifare card types
Energy reporting	Per-session kWh, cost calculation, billing-ready exports	Vendor reporting feature documentation
Multi-vendor integration	Onboarding stations from multiple hardware vendors under one platform	Vendor supported station list + brand-agnostic certification

How to cover each requirement in your tender response

Cover each tender requirement with two elements: a concrete clause in your proposal that names the technology, and a verifiable evidence anchor (certification ID, public registry link, regulatory citation). Vague marketing claims like “industry-leading platform” do not pass evaluation. Specific technical references with primary-source links do.

Sample tender clause

Concrete filters you fail with the wrong CPMS

Three concrete filters disqualify or sink tender responses: a lack of verifiable security certification (TLS via wss not just claimed but certified), single-vendor hardware lock-in instead of brand-agnostic OCPP, and enterprise-tier CPMS with onboarding costs and timelines that price most installers out of the market.

The bundled CPMS objection. A common assumption is that the free CPMS shipped with hardware is enough for tender purposes. It usually is not. Bundled CPMS solutions create three tender risks: they lock you to that hardware vendor’s roadmap, they often lack independent OCA Security certification, and they are not designed for multi-vendor integration. All three are common tender disqualification points. An independent OCPP-compliant CPMS removes the risk.

Real case: how an installer won a tender with ELVO

An installer in our customer base had the chance to install stations at a major client. The tender specification made software a hard requirement: bidders had to include a CPMS solution covering OCPP communication, load management under EPBD Article 14, RFID authentication, and integration with stations the client had previously installed from another vendor.

Without a CPMS, the installer would have been disqualified at the technical-evaluation stage. They selected ELVO, set up a working environment in under an hour, and built their proposal around concrete coverage: OCPP 1.6-J with TLS via wss, OCA-certified registry link as evidence, load management capability demonstrated through a pre-bid clarification call with the procurement team, and a written integration plan for the existing stations.

They won the bid. The client also asked them to integrate the existing stations under the same platform after the new ones went live. The installer kept the entire deployment under one CPMS without needing additional vendor relationships or platform migrations.

What ELVO covers for an EV charging tender

ELVO covers the six standard EV charging tender requirements: OCPP 1.6-J Full, TLS via wss with OCA certification, dynamic load management compliant with EPBD Article 14, RFID authentication, real-time per-session energy reporting, and brand-agnostic multi-vendor integration across 700+ charger models. OCPP 2.0.1 is on roadmap for Q4 2026 as of May 2026.

OCPP 1.6-J Full with TLS via wss. Registered in the Open Charge Alliance public registry: openchargealliance.org/certified-companies/. Certification IDs are visible in the registry for verification by tender evaluators.

Dynamic load management. EPBD Article 14 makes this mandatory for non-residential buildings. For the full installer-targeted explanation of EPBD load management obligations and timelines, see our EPBD Article 14 compliance guide.

Brand-agnostic OCPP. Works with stations from any OCPP 1.6-compliant manufacturer. 700+ verified charger models in production.

Real-time energy reporting. Per-session kWh, cost calculation, billing-ready CSV/API exports.

Multi-vendor integration. Onboard existing stations from a different vendor under the same platform without hardware-side changes.

As of May 2026: OCPP 2.0.1 support is on roadmap for Q4 2026. Most current tenders accept OCPP 1.6-J with TLS via wss. Check your tender specification for explicit 2.0.1 requirements before assuming you need it.

What NOT to put in your tender response

Tender evaluators score on verifiable specifications, not marketing language. Replace generic claims with concrete technical references and public-registry citations. Five common anti-patterns to remove from your draft before submission:

Questions to ask during pre-bid clarifications

Most EU tenders include a pre-bid clarification phase where bidders can ask the procurement office for clarification on specifications. Six concrete questions surface technical ambiguities and shape your response in your favor:

1. “Do you require strict OCPP 2.0.1, or is OCPP 1.6-J with TLS via wss acceptable?” Most tenders do not specify. Ambiguity falls in your favor if you cover 1.6-J well.
2. “What is your migration plan when 2.0.1 becomes standard?” Forces procurement to think long-term and signals your readiness.
3. “Do you accept Open Charge Alliance certification as evidence of OCPP and security compliance?” Saves you from running custom security audits.
4. “Is integration with existing stations from another vendor a hard requirement or an optional capability?” Determines whether you must demonstrate multi-vendor integration or just claim support.
5. “What energy reporting format do you require? CSV exports, API access, or both?” Different requirements have different implementation costs.
6. “Are there any contractual penalty clauses tied to CPMS uptime or audit findings?” Penalty exposure changes how you should structure your CPMS guarantees.

How to prepare before your first tender appears

Tender opportunities surface with short response windows. Installers who prepare proactively respond faster and more credibly. Four concrete preparation actions you can complete this month:

1. Start a 30-day ELVO trial now. Get hands-on with the platform during a quiet period. You will respond faster when a tender opportunity appears with operational capability already in place.
2. Onboard 1-2 projects to your CPMS account. Even a single deployment gives you evidence to cite in future tender responses (“our platform is in production across N sites”).
3. Collect proof artifacts in a shared folder. Save the OCA certification registry screenshot, ISO 27001 certificate, EPBD Article 14 capability documentation, and ELVO platform screenshots. When a tender response is due in 5 days, you do not want to be hunting for these.
4. Draft a reusable tender response template. Use the sample clause in this article as a starting point. Adapt it once. Reuse the structure across multiple tender responses with minor tailoring.

Frequently asked questions

What does a CPMS section in an EV charging tender typically require?

An EV charging tender’s CPMS section typically requires OCPP 1.6-J compliance, TLS-secured WebSocket communications (wss), dynamic load management under EPBD Article 14, RFID authentication, real-time energy reporting, and integration with stations from multiple hardware vendors. Most disqualifications come from missing load management or unverifiable security claims.

Do I need OCPP 2.0.1 in my tender response now?

OCPP 1.6-J is the most widely deployed version in EU EV charging tenders as of May 2026. Most public and private tenders accept 1.6-J with TLS via wss. 2.0.1 is starting to appear in large AFIR-aligned public tenders but remains uncommon. Check the tender for an explicit 2.0.1 requirement; if absent, OCPP 1.6-J coverage with TLS via wss is what matters.

Can I use the free CPMS bundled with my hardware vendor’s stations?

Bundled CPMS solutions often lock you to that vendor’s hardware, lack independent Security certification, and cannot integrate stations from other vendors. Those are three common tender disqualification points. An independent OCPP-compliant CPMS removes that risk.

Can an installer realistically win an EV charging tender?

Yes. Tender wins come from coverage of requirements and credible evidence, not from company size. Installers often win on transparent pricing, brand-agnostic OCPP coverage, and the ability to demonstrate live capabilities through a free trial during pre-bid clarifications.

How fast can I have a working CPMS ready to show in a tender response?

ELVO operates in 5 minutes via self-signup with a 30-day free trial and no setup fee. You can run a live demonstration during pre-bid clarifications, which often carries more weight than written claims.

What concrete questions should I ask the procurement office during pre-bid clarifications?

Ask about the required OCPP version (1.6 vs 2.0.1), acceptance of Open Charge Alliance certification as evidence, whether multi-vendor integration is a hard requirement, the required energy reporting format, and any uptime or audit penalty clauses in the contract.

Read more

• EPBD Article 14 for EV Charging Installers: The 2026-2027 CPMS Compliance Guide

Resources

• EUR-Lex AFIR text (Regulation 2023/1804)
• EUR-Lex EPBD text (Directive 2024/1275)
• Open Charge Alliance certified vendors registry
• Open Charge Alliance OCPP specification page
• eIDAS Regulation (EU 910/2014, updated 2024)

Conclusion

EV charging tenders are won by installers who match requirements with verifiable evidence, not those with the largest marketing budget. The six core CPMS capabilities (OCPP 1.6-J, TLS via wss, EPBD-compliant load management, RFID, energy reporting, multi-vendor integration) are technical specifications you can demonstrate and prove. ELVO is built for installers responding to these tenders: brand-agnostic OCPP, OCA-certified, with a 30-day free trial.