To integrate Tecell’s Charge Management System (CMS) with a new charging cabinet OEM for custom hardware, the primary technical requirements include supporting OCPP 1.6 and 2.0.1 protocols, providing secure API access for real-time communication, and ensuring hardware compatibility with CMS’s standard interfaces. The OEM must also implement proper authentication and data encryption to maintain compliance with charging infrastructure security standards.
Implementation Process and Compatibility
The integration process begins with the OEM providing detailed technical specifications of their hardware, including communication protocols, power delivery capabilities, and physical dimensions. Tecell’s development team then evaluates these specs against CMS’s compatibility matrix to identify any necessary modifications. The OEM must also supply firmware update mechanisms and diagnostic tools that align with CMS’s operational requirements.
Once compatibility is confirmed, the OEM works with Tecell’s engineering team to establish secure API endpoints for bidirectional communication. This includes setting up TLS 1.3 encryption, implementing robust authentication tokens, and configuring webhook integrations for event notifications. The final step involves comprehensive testing in a staging environment to validate all communication flows before production deployment.
Real-World Considerations for Hardware Manufacturers
For OEMs deploying custom hardware, the integration process often reveals unexpected challenges with existing hardware designs. Many manufacturers discover that their current firmware lacks support for OCPP’s advanced features, requiring significant code modifications. The most common issue involves power management protocols that don’t align with CMS’s load balancing algorithms.
Successful integration also depends on the OEM’s ability to provide detailed documentation and maintain consistent communication throughout the process. Some manufacturers struggle with version control for firmware updates, which can cause compatibility issues when CMS releases new features. The key is establishing a clear support channel and regular review cycles to address any emerging technical challenges.
Related Reading
For more on related topics, see: EV Charging CMS – Basic Plan | Tecell.
Further reading: Blog – Tecell CMS