eMobility software engineering partner for EV charging systems

Menu
Technical testing and integration matrix Illustrative matrix of test areas, technical dependencies, and the steps from planning through testing and review to documentation. Check marks show the illustrated checked state, open circles show open items, and crossed circles show items outside the illustrated scope. Tests Unit CSMS Targethardware OCPP Access Metering Firmware Profiles Planning Tests Review Documentation tested open out of scope

ChargeSphere.OCPP

Integration and Validation

The used OCPP version or version scopes, functions, interfaces, and project-specific modifications are defined and documented during technical evaluation.

This page describes the technical steps, documentation outputs, and allocation of responsibilities for the defined ChargeSphere.OCPP operational scope.

Request a technical evaluation

Clarifying the operational scope

A traceable integration plan starts with the constraints of the target architecture. The relevant technical dependencies are systematically assessed before the defined operational scope is documented.

Starting point

Target architecture

The charging station's existing hardware, firmware, system components, and technical boundaries are captured as the starting point.

Communication

Interfaces

The connection between the charging station and the backend system is assessed together with the relevant interfaces and dependencies.

Adaptation

Configuration and diagnostics

Configuration requirements, diagnostic paths, and project-specific modifications are identified and scoped.

Test basis

Test environment

The target system, test configuration, and expected results are defined for testing and validation.

From scope to technical documentation

The process links the technical evaluation to the description of the target architecture, the agreed activities, and the documentation of results.

Clemios supports agreed integration, testing, and validation activities for the defined ChargeSphere.OCPP operational scope.

Technical validation is not equivalent to formal OCPP certification, complete conformance, or universal interoperability.

  1. Capture the starting point

    Technical requirements, system boundaries, and the evaluation objective are gathered and reviewed.

  2. Describe the architecture

    The integration point, interfaces, dependencies, and project-specific modifications are described.

  3. Agree the activities

    Testing and technical validation activities are aligned with the defined operational scope and test environment.

  4. Document the results

    Results, known limitations, and open items are recorded for the defined operational scope.

Technical outputs and documentation

The results to be recorded depend on the defined operational scope. The documentation provides traceability between the operational scope, the test basis, and the known limitations.

The following items describe possible outputs of the technical evaluation and the agreed integration, testing, and validation activities. They do not constitute a standard package that is automatically included.

  • Interface definition

    Defined integration points, assumptions, and technical dependencies.

  • Integration configuration

    Documented configurations and project-specific modifications within the defined operational scope.

  • Test and validation plan

    Documented test environment, verification steps, and expected results.

  • Issue classification

    Observed deviations and open items are classified and documented by severity and status.

  • Technical documentation

    Agreed integration information for technical assessment.

  • Evidence references

    References linking the results to the test basis, operational scope, and known limitations.

Responsibilities within the target architecture

The technical assessment distinguishes the defined ChargeSphere.OCPP operational scope from the tasks and decisions relating to the complete OEM target architecture.

Clemios

  • Defined ChargeSphere.OCPP operational scope
  • Integration information and technical documentation
  • Agreed integration, testing, and validation activities

OEM

  • Target architecture and charging-station hardware and firmware
  • System integration and assessment in the target system
  • Technical acceptance, product approval, and series-production release

Technical acceptance of the agreed operational scope is performed by the OEM.

OEM acceptance is not formal OCPP certification and not general production or series release by Clemios.

Request a technical evaluation

For an initial assessment, it is helpful to provide information about the company, charging station, firmware, backend system, intended operational scope, and test environment.

The technical scope and integration prerequisites are clarified during the technical evaluation.

Request a technical evaluation
Scroll to Top