Back to NX SOLAR

For charge point operators

CPO EV Charging Solution

Bring EV charging hardware and software into one operator-focused project scope, from site equipment and a charging station backend to network visibility and optional operational support.

Charging hardware

Build the Network from the Site Up

Start with charging equipment selected around the site, vehicle demand, operating model and expansion plan. Hardware selection and configuration are confirmed during project assessment.

Site-aligned equipment

Plan charging equipment around the intended use case, site conditions and operator workflow without separating the hardware decision from the network plan.

Coordinated deployment

Define equipment, backend and commissioning requirements as one project scope so stakeholders can prepare a practical rollout plan.

Operational readiness

Connect site planning with the day-to-day needs of the team responsible for network visibility, driver access and service follow-up.

Management platform

Manage Sites through One Charging Station Backend

The EV charging management software brings station information and operator workflows into a shared environment. Available functions and configurations are defined for each project.

Network workspace

Organize stations, users and operating information to support consistent EV charging network operations across the agreed project scope.

Role-based workflows

Structure access for relevant operator teams and business workflows according to the platform configuration selected for the project.

Commercial workflows

Connect Charging Activity with Business Administration

Bring billing, payment, account and reporting workflows into the management environment. Exact commercial functions, payment arrangements and local service dependencies require project confirmation.

Billing

Prepare charging records for the billing workflows defined by the operator and the selected platform configuration.

Payment

Plan payment-related workflows around the selected service arrangement and any required third-party providers.

Accounts

Support agreed driver, customer or business account structures within the configured management environment.

Reports

Review operational and commercial information through reports available within the confirmed project scope.

Remote visibility

Monitor the Network and Organize Diagnostics

Remote visibility can help an operator identify station status, review events and organize service follow-up. Diagnostic depth and available actions depend on the selected hardware, software and project configuration.

  • Station overviewReview available station and network status information from the management environment.
  • Event reviewUse recorded events and available diagnostic information to support triage and follow-up.
  • Service coordinationRoute relevant information to the teams responsible for investigation, maintenance or customer communication.

Connected ecosystem

Plan APIs, Roaming and Third-Party Connections

A CPO may need the charging network to exchange information with other business systems or service providers. Connection requirements are assessed as part of the project rather than assumed as standard.

Configuration-dependent capabilities

API access, roaming, third-party integrations and a white-label EV charging platform are available only where confirmed for the specific project scope, technical environment and commercial arrangement.

  • Document the required data flows and business purpose
  • Confirm technical and third-party dependencies
  • Define testing, ownership and launch responsibilities

Optional operations support

Add Support around the Operator's Own Model

Managed EV charging services may be discussed as an optional part of the wider hardware-and-platform project. Availability, responsibilities and service boundaries depend on the agreed CPO solution scope.

Workflow support

Discuss support for selected operational workflows in relation to the hardware and management platform delivered for the project.

Defined responsibilities

Set clear boundaries between the operator, NX SOLAR and any third-party service providers before implementation.

Implementation

Move from Requirements to an Integrated Rollout

The implementation path aligns site needs, charging hardware, software configuration, connection requirements and operational ownership before launch.

  1. Define the operating modelShare the network goals, user journeys, locations and internal responsibilities.
  2. Confirm the solution scopeAlign hardware, management functions, commercial workflows and required connections.
  3. Prepare implementationAgree configuration, testing, commissioning and stakeholder responsibilities.
  4. Launch and follow upMove into operation with the agreed support boundaries and review process.

Plan Your CPO EV Charging Solution

Tell us about your target sites, operating model, management requirements and project stage. The team can review the scope without assuming unsupported product or integration capabilities.

Start a CPO Inquiry

Frequently asked questions

CPO Solution Questions

Key points to clarify before defining an operator solution.

Is this a standalone EV charging management software offer?

No. This page presents an integrated CPO EV charging solution that brings charging hardware, a management platform and operator workflows into one project discussion.

Can the platform connect to our existing systems?

Potential API and third-party connections must be reviewed against the required data flow, technical environment, provider dependencies and agreed project scope.

Are roaming and white-label options included?

They are not assumed as standard. Roaming and white-label options require confirmation for the specific platform configuration, market context, third-party dependencies and commercial arrangement.

Does NX SOLAR operate the charging network for us?

The operator retains its defined business role. Optional support for selected EV charging network operations may be discussed, with responsibilities and service boundaries confirmed before implementation.