OCPP Native

This document outlines Zaptec's OCPPNative integration, also referred to as "box-level" or "native OCPP" operation, for Zaptec Go chargers. This integration adheres to the OCPP 1.6-J standard, ensuring standardized communication and compatibility with third-party Central Systems.

Access Management and Initial Setup

Zaptec provides specific mechanisms within the Zaptec Portal to manage access and configure chargers for this feature:

• Dedicated Permissions: Administrators can grant specific user permissions related to OCPPNative functionality within the Zaptec Portal.
• Designated Installation Type: Chargers intended for OCPPNative operation must be configured under an "Operator" installation type. This type is specifically tailored for this mode of operation.

Key Benefits

• Direct Charger Control: OCPPNative enables direct command and control of individual Zaptec Go chargers via their configured OCPP link to a third-party Central System.

• ℹ️

  Focus on Core OCPP 1.6-J Functions:

  The integration concentrates on the core functionalities defined by OCPP 1.6-J for direct charger interaction. Consequently, advanced system-level features, such as dynamic load balancing managed by the Zaptec cloud or other centralized services beyond individual charger control, are outside the scope of this OCPPNative mode.

• Continued Cloud Support: Even when operating in OCPPNative mode, Zaptec's cloud infrastructure remains active for essential services:

  • Operational Data Logging: Chargers continue to transmit operational data and diagnostics to the Zaptec cloud.
  • Maintenance and Support Facilitation: This logged data is maintained in the cloud to enable efficient remote support and troubleshooting.
  • Remote Firmware Updates: The Zaptec cloud retains the capability to deploy firmware updates to the chargers.

Configuration for Native OCPP Operation

To configure a Zaptec Go charger for OCPPNative operation:

• The device must be assigned to an installation designated as the "Operator" type within the Zaptec Portal.
• Key configuration parameters include:
  • Management Mode: This must be set to "OCPP (Native)."
  • OCPP Central System URL: Administrators configure this URL, which points to the third-party OCPP Central System, via the Zaptec cloud interface.

For detailed, step-by-step instructions on configuring chargers for OCPPNative operation, please refer to the internal guide: Zaptec Go OCPP Native configuration

Operational Behavior and Limitations

• Power Management: In OCPPNative mode, local (charger-initiated) power management is disabled. All power control and limits are managed by the connected OCPP Central System.
• Authentication: Charger authentication for starting and stopping charging sessions is handled exclusively via the OCPP protocol with the Central System. Zaptec cloud-based authentication methods (e.g., Zaptec App, RFID tags registered in the Zaptec Portal) are bypassed for charging operations in this mode.
• Operational Logging: Charger events, status updates, and diagnostic data continue to be logged by the device and transmitted to the Zaptec cloud as per standard operation.
• Reverting to Zaptec Cloud Management: If a charger's "Management Mode" is changed from "OCPP (Native)" back to a Zaptec cloud-managed mode, or if the installation type is altered, communication with and control by the OCPP Central System will cease. The charger will then revert to management by the Zaptec cloud.