Up to 10 charging stations
At one site, with agreed models and OCPP versions. One existing CPMS remains responsible for charging operations.
NeLeSo OCPP Gateway · Pilot
Turn an evaluation into a defined pilot.
Use your own equipment to evaluate charging operations alongside additional data use. Get a defined scope, measurable acceptance criteria and a basis for your next rollout decision.
Pilot scope
A clear starting scope for your proposal.
This outline is the basis for scoping together. Before starting, we agree the binding scope, price, start date and acceptance criteria in the pilot order.
One additional data destination
Selected meter values or session events to one HTTPS or MQTT destination. One export configuration or suitable workflow and one operational user account form part of the agreed test scope.
A four-week planning outline
Starting once infrastructure and access are ready. Two weeks of observation are planned; binding dates and measurement periods are set in the proposal.
A possible four-week pilot timeline.
- 01
Week 1 · Prepare and connect
Review stations and target systems, establish access and responsibilities, and configure the Gateway. Document the changeover and rollback procedure before starting.
- 02
Weeks 2–3 · Observe and verify
Trace charging sessions and exports, test permissions, and verify an agreed outage of the additional data destination followed by queued delivery.
- 03
Week 4 · Accept and plan
Review results together. Receive the configuration, acceptance report, open items and a proposal for the next rollout step.
Acceptance criteria
Agree what success looks like before starting.
- The agreed stations connect to the CPMS; defined test charging sessions and their OCPP responses can be traced.
- Selected events reach the data destination with verifiable event IDs. Completeness and permitted latency are agreed for the measurement period.
- The agreed data destination outage leaves the primary path unaffected. Queued exports are delivered after recovery, with possible duplicates identifiable.
- The test account can access only permitted stations and data. Actions without permission are rejected.
- Configuration, operating guidance and rollback are documented. Deviations have an owner and an agreed next step.
Clear responsibilities during the pilot and beyond.
Self-hosted
Your IT operates infrastructure, monitoring, backups and recovery, and installs agreed updates. NeLeSo delivers the commissioned application configuration, onboarding and evaluation. Support scope and response times are set in the proposal.
Operational support by agreement
If you need hosting or operational assistance, the proposal explicitly assigns the operator, update windows, monitoring, backup, recovery and support. Managed operations or availability commitments require that agreement.
Pricing and scope boundaries
A pilot order with its own scope.
Pilot pricing depends on the hardware mix, target systems and support needed. Indicative software pricing remains €250 per installation per month plus €1 per active Charge Point ID per month. Optional standard onboarding at €1,900 covers up to two remote person-days; it is not a flat fee for the entire pilot. All amounts exclude VAT.
An assessment workshop is a separate consulting engagement and is not a prerequisite for the pilot. Load management, energy integration and local charging control can be planned in a separate CPMS project if required.
Indicative software pricing and onboardingYour pilot proposal
These details are enough to get started.
Tell us the station count and models, existing CPMS, intended data destination, operating model and preferred start date. The enquiry form is prepared for these details. We clarify open questions and turn them into a concrete pilot proposal.